Current Limitations

Evidence accessibility

warning

The four surveyed implementation repositories are private. The checks below are local results, not public evidence that an external reviewer can reproduce without repository access.

What passing checks do not prove

Result	Does not establish
daejang-jit-engine tests pass	Production RPC behavior or a publishable end-to-end replay
schema make check passes	Any Event, valuation, tax, or report runtime behavior
daejang-db checks pass	Live PostgreSQL integration unless the integration-test database URLs are set
Documentation CI passes	Correctness of the downstream domain engines described as planned

Runtime gaps

• No production-connected exchange adapter has been verified. Standalone parser work is supporting evidence only until it reaches the shared extraction contract, persistence, fixtures, and CI.
• Event, Posting, Valuation, and provenance lot calculation have schema or storage contracts but no domain runtime.
• The generic LotRun does not represent the target resident × tax_year × tax_asset_id inventory or provisional/final run mode.
• No ReportModel, report/Evidence Pack generator, or publication-specific store exists.
• No GIWA contract, schema UID, transaction, or Explorer proof exists.

The end-to-end Golden Path is therefore Planned: evidence → Observation → Event → Posting → Valuation → KR Tax Inventory → Report.

Known schema gaps

• The current LotRun.scope has assetIds, but no typed Korean tax inventory scope or provisional/final run mode.
• #EvidenceManifestData describes publication evidence and closure, but there is no typed report-line model that connects each presented figure to Event, Posting, Valuation, and tax-inventory identifiers.
• #BlockEventKind currently covers BEACON_WITHDRAWAL; other transaction-less protocol events require additive kinds and fixtures.
• Artifact retention classes and EVICTED are modeled, but the v1 implementation intentionally has no automatic eviction worker for ordinary evidence.

Evidence required for the next claims

Required evidence	Claim it would unlock
Public source snapshot or reviewer access	Externally checkable implementation claims
Real RPC fixture and reproducible JIT → schema → PostgreSQL run	Implemented EVM evidence path beyond mocks
Production exchange fixture with complete extraction outcomes	Exchange ingestion
Six Event/Postings MVP fixtures	Interpretation runtime
Exact-ratio price/FX fixtures including missing and conflict cases	Valuation runtime
Pooled annual total-average fixtures and typed TaxInventoryRun	Korean tax inventory
ReportModel, publication store, valid/tampered manifest tests	Report and Evidence Pack
Deployed contract and valid/tampered external verification	GIWA integrity

Documentation verification

CI uses Node 22 and runs dependency installation, TypeScript checks, both locale builds, /docs/ canonical-path assertions, and an admonition-rendering check. Dependency audit output is recorded but does not block documentation builds because the reported advisories are upstream build-time dependencies without an available repository-level fix.