SYSE.7:4.2 - Record the Result
Use a compact EngineeringDescriptionEnsembleAccount@Project when several descriptions materially support one
decision. It is a project-local episteme; the FPF kinds of its participants remain unchanged.
| Field | Required content |
|---|---|
| receiving decision | Decision, decision subject, intended use, interval, and downstream Work that will use the result. |
| decision-changing claims | The smallest claim set whose value, contradiction, evidence, or absence can change the decision. |
| description entries | For each episteme: source and edition, claim content, EntityOfConcern, reference scheme, configuration/effectivity, modeled interval, assumptions, omissions, and relying Work. |
| expression and publication entries | Material carriers, publication occurrences and forms, renderings, executable expressions, database objects, or generated summaries, each kept separate from the source episteme. |
| model-use conditions | Purpose, scale, units, coordinates, tolerances, boundary conditions, parameter sources, interpretation, calculation or inference Method, and validity limits needed by this use. |
| relations | Direct same-subject, part, interface, configuration, source, transformation, evidence, or other governed relations; unsupported correspondence hypotheses are marked as such. |
| collision results | Claim-level agreements, explainable differences, unresolved contradictions, missing interpretations, and missing world-side checks. |
| realization correspondence | Actual configuration or occurrence, observation/evidence basis, and the decision claim it can confirm, weaken, or reopen. |
| maintenance assignments | Assigned Agents, their system-role assignments, authority, capability, Work, and acceptance conditions for producing, checking, changing, or retiring description uses. |
| return and refresh | Receiving Work and the Agents assigned to it, accepted reliance limits, current gaps, triggering observations, and the smallest affected account or decision to reopen. |
The account can be published through, for example, linked text, tables, model queries, a repository view, or generated reports. Its identity and sufficiency do not depend on one storage technology.