Skip to main content

Repository layout

Every topic has one owner. Hubs link to owners; they do not restate architecture semantics.

PathResponsibilityAuthority
asl/arch/Architecture-wide state, types, profiles, memory, and dispatchNormative ASL/NDF
asl/block/Bundle/command instruction and model unitsNormative ASL/NDF
asl/scalar/Scalar instruction and shared scalar-model unitsNormative ASL/NDF
asl/tile/Direct Tile instruction and shared Tile-model unitsNormative ASL/NDF
docs/{arch,block,scalar,tile}/Exact generated mirrors with bounded supplementary proseDerived projection
tests/asl/Independently runnable AVS points mirrored to each ASL ownerExecutable evidence
docs/status/decisions/ADR rationale and reviewed decision metadataDecision record; not current semantic owner
docs/status/open/Unresolved architecture choicesGap record
docs/governance/ADR and validation workflow guidanceProcess policy
docs/development/Contributor setup and repository navigationDeveloper guidance
docs/releases/Release identity and evidence entry pointsRelease navigation
spec/catalog/Accepted-form, register, profile, and selector projectionsDerived machine-readable view
spec/evidence/Commit-scoped traceability and closure recordsDerived evidence
spec/release-inputs.jsonExplicit canonical evidence registryRelease input contract
spec/release-manifest.jsonContent and encoding fingerprintsGenerated release contract
scripts/Deterministic generators and fail-closed checksExecutable repository policy
.github/workflows/Hosted pull-request, nightly, and release lanesHosted executable policy

ASL source order is derived from PTO-UNIT dependency metadata. Test discovery comes from PTO-TEST records in the mirrored tests/asl/ tree. There is no hand-maintained aggregate semantic source or test owner.

Generated exhaustive matrices follow the same ownership rule: one case per result file, one stable PTO-TEST.id, and no hidden multi-case shard. Focused execution selects exact IDs through scripts/print-asl-test-matrix --ids-file; only the release lane plans and validates the complete repository matrix.

Use the architecture overview to enter the formal reference, the ADR process for normative change control, and the release hub for commit-scoped evidence.