[gustavonline]

Project-specific settings could outlive a chat without a clear upkeep owner. Foundation now establishes the existing configuration/adoption record, and that project's AgentOps maintains meaningful persistent choices and exceptions.

Before	After
Installation choices recorded, ongoing ownership implicit	One existing record with an owner, real scope, source and relevant removal/recovery condition
A desired setting could be confused with applied configuration	Requested/approved intent, applied native state and verified behavior stay distinct
Initial delegation advice could start an unbound writer	Writers needing isolation use native worktree-bound launch; binding is checked before edits

No configuration engine, new register format, live Gmail grant or model change. The README clarifies the three responsibilities and one AgentOps per application project, with the requested Arc’ It AI banner.

Validation: 8-skill package check, 11 tests and whitespace checks passed. A fresh native Astra xhigh context passed four textual decision cases on the method commit; these are not live permission tests. An actual unbound AIOS child was stopped before edits and replaced with a verified native-bound writer. Independent native review found and resolved one branding-license documentation issue. Focused follow-up passed at 2b70101; prior unchanged tests, staging, routing case and banner inspection remain dated evidence. Current PR CI passed.

Review focus: the proportionate record in adoption.md, AgentOps upkeep responsibilities, and the launch clarification in t3.md. Delivered as v0.1.10. On the selected execution host, all 48 installed files matched the release; native AgentOps explicitly reread the six changed instructions and verified their hashes. This is not a new Claude automatic-loading qualification.