Project context

AGENTS.md is the portable baseline for project instructions. Each harness consumes it through its own most native path, and uze reports the result instead of guessing:

The commands

$ uze install    # resolve the environment, and leave the context reconciled
$ uze status     # which file the context comes from, and who currently reads it

Reconciling is not a step you perform: uze install ends with it, so declaring an environment and projecting it are one command, and uze status is where you find out whether anything is still owed.

The three operations underneath are on the agent surface, because their answer is region by region and only a writer of AGENTS.md acts on it:

$ uze agent context inspect      # what each harness currently sees — never writes
$ uze agent context plan         # exactly what reconcile would change — never writes
$ uze agent context reconcile    # apply it

reconcile maintains only the delimited regions it owns. Anything you wrote around them is preserved, and a file carrying content outside a well-formed managed region is recognized and reported (VendorLocked), never overwritten.

What lives in a managed region

AGENTS.md is yours; uze owns nothing but the marked blocks inside it.

• package:<name>:instructions — one region per installed package that ships its own AGENTS.md, composed in by reconcile.
• project:worktree-policy — the checkout an agent is already working in, and what this project does with finished work. Its only audience is a writer uze did not place itself: a subagent spawned inside a harness session, which would otherwise isolate a second time on top of the checkout it is already in. See The agent workspace.

Each region is receipt-owned. Drift inside one is reported rather than overwritten, and a region whose owner is gone is removed rather than left behind.

Portability states

• Portable — AGENTS.md exists and every detected harness that needs something from it has it (natively or via a matched bridge).
• Partially portable — at least one harness's bridge is missing or out of date; the report names which.
• Vendor-locked — no AGENTS.md, but vendor-specific files hold their own content. uze makes the split visible instead of papering over it.
• No context — no recognized instructions file at all.