admin/accounting_report
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Consolidate GL-001 TradOn assessment decisions

Browse Source
This commit is contained in:
GiorgioCALLIGARO
2026-05-08 12:31:28 +02:00
parent 4ce9711c3f
commit c344be9dff
13 changed files with 918 additions and 396 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
AGENT.md
View File

@@ -30,6 +30,12 @@ When documents conflict, use this order of authority:
If a conflict remains unclear, document it as an open question instead of silently choosing a business rule.
## Implementation platform context
The accounting reports are intended to run from TradOn, the project-specific customized version of Tryton. Treat TradOn as the selected CTRM / ERP implementation platform.
The baseline exposure is assessed against Tryton capabilities and known TradOn customizations. Report-specific choices such as open-source UI components, exports, calculations or additional TradOn customizations must be arbitrated per report in the relevant `decision_register.md`.
## Working principles
- Keep specifications functional and technology-neutral until a data model is provided.
@@ -144,19 +150,19 @@ When asked to create or refresh a Tradon assessment:
2. Copy the relevant source file into `Assessments/Tradon/<REPORT_CODE>/source_documents/`.
3. Record the intake source and retained assessment copy in `source_material.md`.
4. Keep the target report specification in `Reports/` as the functional reference.
5. Capture exposure notes, gap mapping, open points and decisions in the assessment folder.
6. Do not rewrite the target report silently from the GAP analysis; explicit decisions are required.
7. Write new framing questions in the relevant document using `Q: `, optional `C: ` comments, optional `PROPOSITION: ` proposals and `R: ` user responses.
5. Capture exposure notes, gap mapping and the unified decision register in the assessment folder.
6. Document TradOn-specific implementation choices in `decision_register.md`; do not rewrite the target report silently from the GAP analysis.
7. Write new framing questions in `decision_register.md` with a recommended answer, options, impact and validation expectation.
When asked to prepare development backlog items from gaps:
1. Start from the relevant `Assessments/Tradon/<REPORT_CODE>/gap_mapping.md`.
2. Link each backlog item to stable gap themes, open points and pending decisions.
2. Link each backlog item to stable gap themes and `decision_register.md` question IDs.
3. Keep items atomic enough to be implemented and tested.
4. Include acceptance criteria and expected validation controls.
5. Mark items blocked when a business or mapping decision is still open.
6. Do not invent source tables, joins or implementation design beyond what the assessment evidence supports.
7. Prefer linking backlog dependencies to pending decisions (`PD`) rather than directly to open questions (`Q`) once a decision wrapper exists.
7. Prefer linking backlog dependencies to the stable question IDs in `decision_register.md`; do not create separate pending-decision wrapper IDs unless explicitly requested.
## Boundaries