Implemented Infrastructure
Daejang's implemented technical foundation has three responsibilities: reconstruct EVM execution evidence, keep the resulting records structurally valid, and preserve revisions and lineage for later review.
This page shows how those responsibilities fit together without exposing internal service or package details.
The EVM evidence and Observation path shown here is Implemented. Event interpretation, Posting, Valuation, tax inventory, and Report generation remain Planned and are described under Product Roadmap.
How the implemented components fit together
Solid arrows show the primary movement of data. Dashed arrows show shared contracts. Schema is not presented as a separate business-computation runtime: it defines the structures and invariants that evidence and stored records must satisfy.
Component responsibilities
| Component | Responsibility | Deliberate boundary |
|---|---|---|
| JIT Engine | Verify the request context, collect execution artifacts, and normalize supported account-scoped facts into Observations | Stops before economic or tax interpretation |
| Schema contracts | Define evidence, Observation, ledger, lot, and publication structures and validate their invariants | Validation does not calculate Event, Valuation, inventory, or Report results |
| Persistence layer | Store immutable artifacts, terminal outcomes, revisions, and lineage through typed PostgreSQL boundaries | Storage accepts domain results produced elsewhere; it does not produce them |
What happens to one candidate
- The JIT Engine checks whether the request and chain context are suitable for reconstruction.
- Available transaction, receipt, log, and trace data are preserved as canonical evidence.
- Supported account-scoped facts become Observations; unsupported, partial, or failed cases receive an explicit terminal outcome.
- Evidence, Observations, revisions, and lineage are persisted so later stages can consume them without replacing the original record.
The detailed behavior is split across JIT Evidence Reconstruction, Evidence & Ledger Contracts, and Persistence, Revision & Lineage.