andersalm · Sep 30, 2026 · Sep 11, 2026 · Sep 11, 2026 · Sep 11, 2026 · Sep 11, 2026
diff --git a/.cargo/config.toml b/.cargo/config.toml
@@ -0,0 +1,10 @@
+[build]
+# Shared intermediate build dir for every workspace in this repo (elastos/,
+# capsules/*, elastos/tools/*): dependency artifacts, fingerprints, and
+# incremental state compile once and land in one CI-cacheable path.
+# Final artifacts (binaries, test executables' uplifted outputs) stay in each
+# workspace's own target dir, so every existing target/{debug,release} path
+# keeps working. Config-relative, so this resolves to <repo>/target-build
+# from any subdirectory. Requires cargo >= 1.91 (build-dir stabilization),
+# which rust-toolchain.toml pins.
+build-dir = "target-build"
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
diff --git a/.gitignore b/.gitignore
@@ -1,6 +1,8 @@
 # Rust
 **/target/
 /target-capsules/
+# Shared intermediate build dir (root .cargo/config.toml build-dir)
+/target-build/
 **/*.rs.bk
 # Main Cargo.lock committed for reproducible builds; negate the ignore
 !elastos/Cargo.lock
@@ -74,6 +76,9 @@ __pycache__/
 
 # --- Operator-local / internal tooling (not part of public runtime) ---
 
+# Private operator evidence receipts
+/.audit/
+
 # Fabro workflow orchestrator (internal ops)
 fabro/
 fabro.toml
@@ -88,8 +93,9 @@ archive/
 control_graph/
 control_graph_viewer/
 
-# Website deployment artifacts
-website/
+# Website deployment artifacts; the public site's source is versioned.
+website/*
+!website/elastos/
 
 # AI models
 models/

diff --git a/AGENTS.md b/AGENTS.md
diff --git a/PRINCIPLES.md b/PRINCIPLES.md
@@ -177,6 +177,12 @@ access policy.
   end-to-end cryptography remain above Carrier, and compatibility transports
   stay provider-internal
 
+The target [storage and access contract](docs/STORAGE_AND_ACCESS.md) applies
+these constraints to encrypted private objects, protected use, explicit export,
+revocation, and recovery. Its
+[implementation guide](docs/OBJECT_PROTECTION_IMPLEMENTATION.md) keeps storage,
+rights evidence, and key mechanisms replaceable behind Runtime authority.
+
 ## 16. UI surfaces must not be authority
 
 Opening a page and holding a capability are different things.

diff --git a/README.md b/README.md
@@ -8,26 +8,25 @@ For released versions, supported installation targets and known limitations,
 see [state.md](state.md). A source checkout and a published installation have
 separate artifact identities and verification records.
 
-## Install the Linux preview
+## Install from the publisher
+
+The public installer looks up signed releases for Linux x86_64/aarch64 and macOS Apple silicon. Intel Mac and other OS families fail closed.
 
 ```bash
 curl -fsSL https://elastos.elacitylabs.com/install.sh | bash
-export PATH="$HOME/.local/bin:$PATH"
-elastos setup
-elastos
 ```
 
-Running `elastos` opens Home. The default setup installs Home and its core Apps.
-You do not need a separate `elastos serve` process for this path.
-Home is the user-facing front door to the managed Runtime.
+The installer installs Runtime, sets up the Home profile, and opens Home. Keep
+the terminal open while you use Home. Add `$HOME/.local/bin` to PATH when you
+later run `elastos` from a new shell. You do not need a separate `elastos serve`
+process for this path. Home is the user-facing front door to the managed
+Runtime.
 
 Only one live host may own an ElastOS data home at a time. Stop Home before
 using the separate operator runtime in the same home. See [Installing
 ElastOS](docs/INSTALL.md) for profiles, updates, trust verification, and
-operator setup.
-
-macOS currently uses source-home staging rather than the public installer. See
-the [Mac staging runbook](docs/MAC.md).
+operator setup. See the [Mac staging runbook](docs/MAC.md) for source-home
+staging and Browser VM work.
 
 ## Build from source
 

diff --git a/ROADMAP.md b/ROADMAP.md
@@ -1,7 +1,8 @@
 # ElastOS Runtime roadmap
 
-This roadmap describes future work. See [TASKS.md](TASKS.md) for active work
-and [state.md](state.md) for current behavior.
+This roadmap describes future work. See [TASKS.md](TASKS.md) for active work,
+[deferred work](docs/DEFERRED_WORK.md) for the open backlog, and
+[state.md](state.md) for current behavior.
 
 ## Mission
 
@@ -94,6 +95,12 @@ audited reassignment that verifies the root and its protectors before mutation.
 Hosted, loopback, native, and mobile hosts need explicit origin or host-auth
 policy; none may gain authority from a trusted header.
 
+Public first-owner enrollment must start from one-use local operator authority
+and bind one exact HTTPS origin and RP before the ceremony begins. Adding a
+credential to an existing owner requires explicit self-link consent and keeps
+the same principal and protected root. Both flows reuse Runtime auth state and
+produce typed denial, replay, expiry, concurrency, and audit results.
+
 Principal-root protection should use random per-principal data keys. Protectors
 may include a Recovery Kit, client-side WebAuthn PRF wrapping, DID-backed
 recovery, and future quantum-resistant envelopes. Runtime stores wrapped
@@ -133,19 +140,32 @@ in the UI. Recipients verify it before retaining, mounting, or forking it.
 The contract and its limits live in
 [Content availability](docs/CONTENT_AVAILABILITY.md).
 
+The first package-delivery milestone was planned around a signed,
+CID-identified Qwen content capsule. That wording is historical: later
+receipts record installed Qwen and SmolLM2 journeys on named Homes. Current
+acceptance and target limits are in [state.md](state.md#current-model-foundation-23-september-2026-utc)
+and [TASKS Now](TASKS.md#now). The intended experience uses Marketplace
+discovery and exact handoff into Assistant, keeps the selected local model,
+and provides recoverability-aware removal in System. The contract lives in
+[Content capsule distribution](docs/CONTENT_CAPSULE_DISTRIBUTION.md).
+Execution and proof dependencies live in
+[TASKS Now](TASKS.md#now).
+
 ### 3. Build Runtime-mediated protected content
 
 The target protected-content design uses the same effect path as ordinary
 content:
 
-`viewer -> Runtime -> rights provider -> custody providers -> decrypt provider`
+`viewer -> Runtime -> custody nodes (node-local rights) -> decrypt provider`
 
-Runtime will resolve the content object, check availability, verify rights,
-request recipient-encrypted custody contributions, create a scoped decrypt or
-render session, and record the result. Each dependency will have a typed
-contract and fail closed. Viewers will receive scoped output or a scoped
-session, not content keys, custody shares, chain RPC, Wallet authority, storage
-APIs, provider routes, network locations, or credentials.
+Runtime will resolve the content object, check availability, load the exact
+Chain policy, and ask each selected custody node to evaluate rights locally
+before it returns a recipient-encrypted contribution. Runtime then creates a
+scoped decrypt or render session and records the result. Each dependency has a
+typed contract. Every invalid or unavailable dependency fails closed. Viewers
+will receive scoped output or a scoped session, not content keys, custody shares,
+chain RPC, Wallet authority, storage APIs, provider routes, network locations,
+or credentials.
 
 The dependency order is contracts and cryptographic review, private provider
 protocols, Wallet/Chain authority, durable Runtime coordination, then installed
@@ -232,7 +252,7 @@ must remain fast and usable without a remote round trip. Carrier and providers
 carry remote synchronization, sharing, and repair.
 
 The namespace contract lives in [Namespaces](docs/NAMESPACES.md). Open syntax
-and provider questions stay in [Tasks](TASKS.md).
+and provider questions stay in [deferred work](docs/DEFERRED_WORK.md).
 
 ### 6. Establish signed capsule publication and installation
 
@@ -399,7 +419,7 @@ contract, but they do not define the native model.
 
 See [People and conversations](docs/PEOPLE_CONVERSATIONS.md) for the target
 model and ordered implementation slices, and
-[Tasks](TASKS.md#collaboration-and-messaging) for open outcomes.
+[deferred work](docs/DEFERRED_WORK.md#collaboration-and-messaging) for later outcomes.
 
 ### 10. Keep release, install, share, and sites on truthful paths
 
@@ -489,7 +509,18 @@ It must not create a separate trust root or expose key material to apps.
 
 AI providers and agents need explicit identity, capabilities, budget policy,
 data access, and audit. Hosted credentials stay inside configured providers.
-Local and hosted models should expose the same typed Runtime contract.
+Local and hosted models use the same typed Runtime contract. Chat Completions
+and Responses adapters have fixture coverage; real configured provider
+compatibility and installed lifecycle proof remain open.
+Installed provider acceptance precedes service publication. Runtime publishes
+the operator-selected signed offer and owns principal-scoped grants. The
+destination Runtime authorizes each remote request, and Carrier transports only
+the route that Runtime selected. Local-engine sharing and hosted-API sharing
+have separate acceptance tracks in [Model provider](docs/MODEL_PROVIDER.md).
+Carrier ingress bounds and destination-owned remote authority precede peer
+acceptance. Hosted-sharing policy and full Jetson target proof remain requested
+work with credential, terms, access and hardware prerequisites, even when source
+review publication occurs earlier.
 
 Operator tools should derive decisions from source, signed artifacts, and
 machine-readable evidence. Durable docs should record contracts and current

diff --git a/SECURITY.md b/SECURITY.md
@@ -43,7 +43,7 @@ request-size cap or read deadline at that boundary. The I/O bridge rejects
 complete lines above 1 MiB, but its line readers allocate before that check.
 Size checks after reading do not bound memory use or an incomplete frame's
 lifetime. Add bounds while reading, with oversized and slow-frame tests;
-the Carrier integration task is tracked in [TASKS.md](TASKS.md#deferred-source-integration).
+the Carrier integration task is tracked in [deferred work](docs/DEFERRED_WORK.md#retained-source-integration).
 
 ## Resolved Findings