Center the agent thesis and define a controlled Agent Task Proof

[ramen-implementer]

Summary

Center the public documentation on the agent interaction thesis and define a controlled Agent Task Proof before S14 expansion. The proof separates Linux scoped shell, Linux typed, and RamenOS typed effects, with protocol-equivalent typed controls, normalized authority manifests, and distinct completion, authority, cost, and audit/replay claims.

Clarify host, QEMU, simulation, and target-architecture boundaries throughout the README and Platform Overview. Split physical H0–H3 from independent software SW0 work, refresh contributor guidance, and move operator details into a development reference. Update the appliance gate's queue labels while preserving the serial-before-graduation assertion.

Pillar / slice

Documentation and SW0 planning, plus a three-line HIL appliance gate label adjustment. No Agent Task Proof implementation is included.

Evidence

• just s11, just s12, just s13, and just foundry-org-governance-g0: passed in default hardware-free modes.
• just foundry-semantic-state-s10-2: passed during the initial documentation pass.
• Local links, runnable command references, shell syntax, and git diff --check: passed.
• Full CI for reviewed head 1a751dd: passed, including the heavy Foundry job and merge gate.
• Evidence remains host tests, QEMU, replay, and planning. No comparative agent result or physical graduation is claimed.

Claim-boundary check

• Does not claim metal graduation, security readiness, or release readiness beyond its evidence.
• No native interface or generated-code change.
• Preserves kernel, service, and Store boundaries.

Docs

• Current Status and Changelog updated.
• No Constitution change; experiment choices and implementation boundaries are recorded in the proof plan.

Separation of duties

Opened by ramen-implementer[bot]. The maintainer's supplied independent review approves exact head 1a751ddc4d7d8af2d784a6b3daacd66fffe6e5ec for merge; approval and merge use the separate maintainer identity.

Follow-ups retained for Phase A

• Define holder-requestable authority as obtainable without a new independent authorization decision.
• Define epsilon on the geometric mean cost-ratio scale.
• If a powered final study exceeds budget, require an explicit review decision on exploratory evidence before treating Phase B as satisfying the S14 prerequisite.

[maxwellsantoro]

Recording the maintainer approval supplied in the review for exact commit 1a751dd: "This revision closes the substantive concerns from my last review. I would merge 1a751dd."

The holder-requestable authority definition, epsilon scale clarification, and infeasible-powered-study decision remain Phase A/execution follow-ups and do not block this approved patch. Merge remains conditional on the required PR checks passing.