quixos-toolchain/quixos-protocol
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Document package architecture and organize current guidance and project backlog

Browse Source
This commit is contained in:
Timothy J. Aveni
2026-10-09 10:33:39 -07:00
parent 0a7bdf7657
commit 041a9e26ad
1 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/execution-world/README.md
+11 -5
View File
@@ -1,5 +1,11 @@
# Closed execution plans and artifacts # Closed execution plans and artifacts
This page documents current compiler/runtime representations. Its universal
artifact inventory, React metadata and overlapping world/installation structures
are [known architectural gaps](../../../docs/ARCHITECTURE_STATUS.md), not the
[core package contract](../../../docs/ARCHITECTURE.md). Historical LF task numbers
refer to the original implementation sequence, not an active queue.
`compileExecutionPlan` validates a workspace, links its checked queries, resolves `compileExecutionPlan` validates a workspace, links its checked queries, resolves
public forwarding, and emits one versioned plan with an SHA-256 digest. It retains public forwarding, and emits one versioned plan with an SHA-256 digest. It retains
exact interface/package revisions and generic applications, owner initialization, exact interface/package revisions and generic applications, owner initialization,
@@ -60,11 +66,11 @@ the core codec's canonical ordering and domain-separated SHA-256 framing. The
monorepo `camino-execution-world` check compares the compiler and core implementations. monorepo `camino-execution-world` check compares the compiler and core implementations.
No machine-local Nix path enters the world descriptor. No machine-local Nix path enters the world descriptor.
The current binding schema is the closed workspace schema. This is conservative: Reusable package compilation now receives a canonical per-package build contract;
an unrelated contract change can require checking/rebuilding several packages. exact source provenance and workspace linking remain separate. See
LF-05 may narrow it to exact checked per-package closures, but must use the same [package build contracts](../../../docs/PACKAGE_BUILD_CONTRACTS.md). Generation,
schema for generation, receipts, and world validation. It must not substitute an receipts and checking must agree on that contract; unchanged source alone does
older package schema just because the source revision did not change. not justify reusing an incompatible binding schema.
## Transaction-port ABI ## Transaction-port ABI