Tradon Exposure Assessments

This folder documents the exposure of target accounting reports to Tryton / Tradon capabilities.

The purpose is to keep report specifications in Reports/ clean and stable, while documenting separately:

coverage identified in Tryton / Tradon;
functional or technical gaps;
mapping assumptions;
open questions;
decisions taken after review.

Scope and limits

The current assessments are based on external analysis documents and available documentation. They should not be read as direct validation of the live Tradon implementation unless this is explicitly stated in the relevant assessment.

For GL-001, the source analysis refers to Tryton / Tradon source files, but the current repository does not include that code. The assessment therefore preserves the evidence and conclusions as documented in the external GAP analysis.

Structure

Each exposed report should have its own folder:

Assessments/
  Tradon/
    <REPORT_CODE>/
      source_documents/
      exposure_notes.md
      gap_mapping.md
      open_points.md
      decisions.md
      source_material.md

Source material intake

Initial GAP analysis files for each report are received in the repository root folder Tradon/. These files may be pushed by another Git user and should be treated as incoming source material.

When an assessment is created or refreshed on request, copy the relevant GAP analysis file from Tradon/ into the assessment folder under:

Assessments/Tradon/<REPORT_CODE>/source_documents/

The assessment process does not change after intake: use the copied repository source as the retained evidence, document traceability in source_material.md, and keep the analysis outputs in the assessment files.

File roles

File	Role
`exposure_notes.md`	Narrative summary of the exposure and main conclusions
`gap_mapping.md`	Structured gap mapping by functional area
`open_points.md`	Questions, assumptions and confirmations still required
`decisions.md`	Decisions and arbitrations taken after review
`source_material.md`	Source documents, date, scope and traceability notes

Open question notation

Open questions must be written in the relevant assessment document, except when the user explicitly asks to handle them elsewhere.

Use these prefixes:

Prefix	Meaning
`Q:`	Open question requiring user, business or technical arbitration
`C:`	Comment that clarifies the open question, context or constraint
`PROPOSITION:`	Accounting-compatible proposal suggested for arbitration
`R:`	User response or confirmed answer

After a document review, any new framing question should be added to the document using the same notation, unless an explicit exception is requested.

Expected file usage:

open_points.md is the register of open questions. It should contain the Q: entries and, when useful, related C: comments or PROPOSITION: proposals.
decisions.md is the register of answers and arbitrations. It should contain the user's R: responses, the selected decision, rationale, impact and validation expectation.
A question may remain Open in open_points.md until the linked decision in decisions.md is confirmed.
When a decision is confirmed, update the linked backlog items according to the development readiness rule.

Recommended statuses

Status	Meaning
`Open`	Gap, question or mapping still to be reviewed
`Confirmed`	Interpretation confirmed by source evidence or stakeholder review
`Accepted Gap`	Gap accepted without immediate change
`Requires Change`	Report specification or implementation must be adjusted
`Out of Scope`	Item acknowledged but excluded from the current scope

Documentation principle

Reports/ remains the target functional specification.

Assessments/Tradon/ documents the comparison with Tryton / Tradon and should not silently redefine the target report. Any change to a report specification should be made explicitly in the relevant Reports/ file and, where useful, recorded in the assessment decisions.md.