Default to native execution and report independently accepted work

.codex/INSTALL.md

@@ -1,35 +1,37 @@
 # Installing AgentOps for Codex
 
-AgentOps 3.3 uses one canonical checkout and source symlinks. Do not use the
-old curl installer or a Codex plugin cache.
-
-## Installation
+Use native Codex and the shell with zero mandatory AgentOps skills:
 
 ```bash
-brew tap boshu2/agentops https://github.com/boshu2/homebrew-agentops
-brew install agentops
-git clone https://github.com/boshu2/agentops.git ~/.local/share/agentops
-cd ~/.local/share/agentops
-ao skills link
+go install github.com/boshu2/agentops/cli/cmd/ao@latest
+ao quick-start
+ao demo
 ```
 
-`ao skills link` creates source links under `~/.agents/skills` and every
-detected runtime skill root, including `~/.codex/skills`.
+Give Codex a concrete outcome and the repository's acceptance checks. A fresh
+context reviews the completed change. No RPI invocation, skill bundle, hook or
+`ao init` is required.
 
-## Verification
+## Optional guidance
 
-Restart Codex and confirm AgentOps skills are visible (for example `/plan` or
-`/quickstart`).
-
-## Update
+From a source checkout, link only the skills you want to make discoverable:
 
 ```bash
+git clone https://github.com/boshu2/agentops.git ~/.local/share/agentops
 cd ~/.local/share/agentops
-git pull --ff-only
-ao skills link
+ao skills link --skill test --skill refactor --dry-run
+ao skills link --skill test --skill refactor
 ```
 
-## Migration from 3.x
+The command links canonical sources into `~/.agents/skills` and detected
+runtime roots, including `~/.codex/skills`. Restart Codex if it snapshots its
+inventory at startup. It does not remove existing skills or replace foreign
+entries. No-selector `ao skills link` still links the full catalog.
+
+Managed plugins and npx full bundles remain supported optional installations.
+Choose one source for a skill to avoid duplicate discovery. Updating a source
+checkout updates its existing links; repeat the same selectors to restore them.
 
-See [docs/MIGRATION.md](../docs/MIGRATION.md). Remove any old
-`~/.codex/plugins/cache/agentops-marketplace` install before linking.
+See [installation and updates](../docs/install-day2-ops.md) for Homebrew,
+building development features from source, full bundles and removal, and
+[migration](../docs/MIGRATION.md) for legacy installations.

AGENTS.md

@@ -2,19 +2,24 @@
 
 Detailed workflow mechanics: [docs/agent-workflow-reference.md](docs/agent-workflow-reference.md).
 
-AgentOps is the operations layer for agentic engineering: skills and evidence
+AgentOps is the operations layer for agentic engineering: tools, optional skills and evidence
 contracts that make one coding-agent change independently judgeable. Your
 tracker, Git, and coding agents keep owning work, history, and execution;
 AgentOps joins them as a federated integration graph and adds the judgment
-step, one RPI traversal at a time:
+step. The default is native execution with zero mandatory AgentOps skills:
 
 ```text
-RPI charter -> on-demand Plan -> Implement and checks -> fresh Validate -> finish
+Accepted intent -> native implementation and checks -> fresh independent judgment -> finish
 ```
 
 No fresh independent judgment over the exact subject means the experiment is
 not proven.
 
+Use the existing issue or conversation, edit the smallest useful change, run
+the repository's checks, and have a fresh context judge acceptance. Load a
+skill only for a concrete uncertainty or an explicitly selected workflow.
+Native goals supply continuity; BD keeps work and handoffs. Neither needs RPI.
+
 ## Repository map and mechanics
 
 | Path | What it is |
@@ -147,7 +152,7 @@ Skill logic ships in Go via `ao`;
 `skills/*/scripts/**/*.py`. Skill tests retain their documented exemption
 (ADR-0016, gate-enforced).
 
-## Lean RPI operating charter
+## Native execution and optional Lean RPI operating charter
 
 Own the authorized outcome through finish. Use the existing accepted intent and
 scope; a clear trivial change needs no Plan, Recall or Learn worksheet. Take the
@@ -178,19 +183,15 @@ out-of-scope change or failed acceptance means `FAIL`. Repair known findings
 within authority and real bounds, then revalidate the changed exact subject.
 Persist machine evidence only for a caller request or declared consumer.
 
-[Memory](skills/memory/SKILL.md) is optional and on demand: recall applicable
-reviewed external topic pages, or separately budget mining/learning and curation.
-BD owns work/status/handoffs, Git content, and native/CASS systems episodes.
-Reuse existing topic pages; entries give applicability, action, support, limits
-and invalidation. One incident supports a narrow observation; stronger rules
-need stronger evidence. Preserve rare useful constraints and legacy `.agents/`
-evidence; no blind TTL/deletion. Learning may remove rules and no-change is valid.
-Benefit requires later work evidence, not saved pages. This lean path accepts
-public or already-cleared trial inputs only and claims no native enforcement
-for restricted sources. Protected external drafts and exact independent support
+[Memory](skills/memory/SKILL.md) optionally recalls reviewed external topic pages
+or separately mines and curates them. Its contract owns support, applicability,
+invalidation and preservation; no blind TTL/deletion. Benefit needs later work
+evidence. Public or already-cleared inputs only: this path supplies no native
+restricted-source enforcement. Protected external drafts and independent support
 and destination-disclosure review precede Git import (ADR-0016).
 
-The [RPI skill](skills/rpi/SKILL.md) owns the charter; the
+The [RPI skill](skills/rpi/SKILL.md) packages this charter when explicitly selected;
+it is not a prerequisite for native execution or independent review. The
 [architecture reference](docs/architecture/rpi-traversal.md) owns exact evidence
 semantics. Optional outer-goal guidance and the grandfathered fixed-dispatch
 reference adapter stay outside the native core. No scheduler or new AO command

GOALS.md

@@ -21,7 +21,7 @@ explicit behavior
 1. **Behavior before activity.** The caller-owned intent states the active
    behavior, acceptance examples where useful, non-goals, evidence, and bounded
    write scope before implementation begins.
-2. **Bounded implementation.** Implement makes and checks the change, repairing
+2. **Bounded implementation.** The native agent makes and checks the change, repairing
    known defects directly within the accepted scope and allowance. Aggregate
    budgets and delivery authority remain with the caller or selected runtime.
 3. **Fresh judgment.** PASS requires explicit, distinct author and validator
@@ -32,10 +32,10 @@ explicit behavior
 5. **Honest uncertainty.** Mutation, incomplete changed-path coverage, missing
    identity, or missing proof returns NOT_PROVEN. Proven scope or acceptance
    failure returns FAIL.
-6. **Sovereign proof.** When requested, Validate atomically writes
+6. **Sovereign proof.** When requested, the fresh reviewer uses AO to atomically write
    content-addressed JSON to caller-selected protected external non-Git storage.
    Preserve legacy evidence under owner policy. Provenance is optional audit.
-7. **Stop boundary.** RPI owns the authorized outcome, using Plan only when
+7. **Stop boundary.** The native agent owns the authorized outcome, planning only when
    needed and revising approach within unchanged acceptance. Known defects get
    direct repair; a causal stall gets at most one bounded fresh helper inside
    the existing allowance. Finish when accepted and freshly validated, or stop
@@ -46,15 +46,16 @@ explicit behavior
 
 ## Structural constraints
 
-- Core hard dependencies are only `rpi -> {plan, implement, validate}`; these
+- Native execution requires zero AgentOps skills. When selected, RPI's
+  core hard dependencies are only `rpi -> {plan, implement, validate}`; these
   capability references do not require invoking every skill on every change.
 - Memory, Learn and all strategy/factory/specialist skills are optional.
 - Core schemas contain no retry, budget, queue, claim, lease, admission,
   next-action, closure, release, or delivery state.
 - The pure manifest and verdict helpers make no Git, tracker, queue, network,
   release, or delivery call.
 - Deterministic `ao gate check` reports repository check success or failure only.
-- Semantic validation is a skill responsibility, not a CLI state machine.
+- Semantic validation belongs to a fresh reviewer; Validate is optional guidance.
 
 ## Gates
 
@@ -88,8 +89,9 @@ evidence for them.
 
 The selected CDLC (Context Delivery Lifecycle) contract maintains external
 context/environment around disposable agents; it neither trains weights nor
-promises deterministic inference. Discovery (with Plan as shaping owner),
-Implement and Validate operate within caller-owned intent and allowance.
+promises deterministic inference. Discovery, implementation and independent
+validation operate within caller-owned intent and allowance. Their corresponding
+skills are optional.
 Optional Memory recall and mining are skill guidance, not a new runtime or
 automatic private-source authorization; evolve restoration belongs only to
 T25. No unavailable entrypoint is enabled by this document.

PRACTICE-REGISTRY.md

@@ -149,33 +149,29 @@ an AI agent with a finite context window, not just a human team.
 The constraint changes the *size* and *shape* of the artifacts those
 practices produce. The practices themselves do not change.
 
-## What the agent-context constraint changes
-
-1. **Granularity** — smaller modules, shorter ADRs, tighter bounded contexts,
-   more snapshots. Each artifact must fit one context window.
-2. **Linkage over inclusion** — artifacts forward-reference rather than
-   embed; agents follow links lazily.
-3. **Discovery surfaces are mandatory** — an `INDEX.md` is not optional, it
-   is the entry point. A skill without an index is invisible.
-4. **Drift is fatal** — human teams could tolerate documentation lag; agents
-   follow stale signposts blindly, so a stale signpost actively misleads.
-   The forcing functions DevOps invented for code and infrastructure now
-   apply to *every* signpost.
-5. **Verification is the spec** — TDD/BDD wasn't optional before; it's
-   load-bearing now because agents trust the verifier, not the prose.
-   A slice without a snapshot or property test is wishful thinking.
-6. **Knowledge compounds, or it actively rots** — agents are stateless
-   between sessions. Without a structured way to capture and recall what was
-   tried, why it changed course, what evidence mattered, every session
-   starts from zero. The practices that worked for human teams still work,
-   but the cost of skipping them is now immediate, not eventual.
-7. **Intent must be linked through phases** — humans can carry intent in
-   memory, side conversations, and organizational context; agents cannot rely
-   on any of that. Discovery intent must become planning packet, council
-   verdict, implementation contract, validation evidence, and handoff without
-   depending on chat history. In AgentOps, the packet is the linked-intent
-   object: it carries the objective, constraints, evidence rules, and
-   provenance anchors from one phase to the next.
+## Applying the registry to native execution
+
+Select practices for the concrete engineering problem; this catalog is not a
+mandatory workflow. For this repository's native default:
+
+- Use BDD examples to clarify ambiguous behavior, including consequential edge
+  cases. A small clear change can use the existing issue and tests directly.
+- Use DDD to keep work tracking, source content, execution, evidence and memory
+  with their existing owners. Introduce an abstraction only for a real boundary.
+- Prefer small batches, direct repairs and tests at the changed behavior's seam.
+  A behavioral fix benefits from a right-reason failing test; a documentation
+  edit does not need a manufactured RED or an executable test of every sentence.
+- Link to current sources and retrieve them on demand. An index earns its cost
+  when it solves an observed discovery problem; no per-task INDEX or packet is
+  required.
+- Run the repository's required integration checks and obtain one fresh review
+  of the exact accepted change. Review depth follows risk and unresolved facts.
+- Reuse reviewed external knowledge when applicable. Preserve support and
+  limitations; later task evidence must establish benefit. Capturing a lesson
+  does not itself prove compounding.
+
+A native goal and existing tracker can preserve intent and handoff facts.
+Discovery, planning, implementation and review do not each need a new artifact.
 
 ## What does NOT change
 
@@ -192,33 +188,16 @@ practices produce. The practices themselves do not change.
 
 ## Implication for this repo
 
-Every artifact under `skills/`, `hooks/`, `evals/`, `docs/`, `schemas/`,
-`scripts/`, and `cli/` is exactly one of:
-
-1. A **bounded context** — a Primitive in our domain vocabulary
-   (`skills/domain/references/primitive.md`)
-2. A **spec** — a Slice, ADR-shaped and BDD-flavored
-   (`skills/domain/references/slice.md`)
-3. A **verification** — a test, a snapshot, an eval suite, a hook gate
-4. A **discovery surface** — an INDEX, a manifest, or a signpost README
-
-Each artifact is sized to fit one agent context window. Each forward-links
-to others. Each has a forcing function (snapshot hash, property test, schema
-check, eval suite) that fails when reality drifts from intent.
-
-Those four artifact kinds are not isolated. Each belongs to an intent chain:
-source material -> packet -> briefing -> verdict or plan -> execution packet
--> validation evidence -> handoff or learning. If an artifact changes the
-work, it must make clear what prior artifact it consumed and what next phase,
-artifact, or operator it feeds. Provenance and trace are how the chain remains
-auditable after the session that created it is gone.
-
-When you build something new in this repo, ask: which of those four kinds is
-this? If the answer is "none", the artifact is probably misplaced. If the
-answer is "all four", the artifact is too large.
-
-That is the practice. AgentOps is its codification under the
-AI-context-limited constraint.
+Keep artifacts with their source owner: code, tests, contracts, and only the
+navigation or evidence a real consumer needs. Before adding process material,
+name that consumer, the decision it supports, the observed defect and the
+condition under which it can be retired. A new program written only to consume
+an otherwise unnecessary artifact does not justify it.
+
+Use the smallest acceptance-advancing action. None of these practices requires
+installing or invoking an AgentOps skill; skills are optional guidance for
+specific uncertainties. The registry does not prove that every practice helps
+every task or that the skill library outperforms native model judgment.
 
 ## Practice slugs (canonical registry)
 

PRODUCT.md

@@ -1,5 +1,5 @@
 ---
-last_reviewed: 2026-09-09
+last_reviewed: 2026-09-10
 ---
 
 # AgentOps
@@ -16,7 +16,7 @@ handoffs — and the product boundary is deliberately small. The standard
 traversal through the graph is:
 
 ```text
-RPI charter -> on-demand Plan -> Implement and checks -> fresh Validate -> finish
+Accepted intent -> native implementation and checks -> fresh independent judgment -> finish
 ```
 
 ## Proven floor
@@ -49,7 +49,13 @@ AgentOps for delivery permission.
 
 ## Product surfaces
 
-RPI carries the operating charter; four skills are loaded as needed:
+The default uses the coding agent and shell with zero mandatory AgentOps skills.
+The repository brief supplies acceptance, source boundaries and required checks.
+`ao` supplies deterministic tools on demand. A native goal can maintain
+continuity; the caller's tracker keeps work and handoffs.
+
+The existing skill library remains optional. Select guidance when a task needs
+it; an explicit RPI workflow packages these operations:
 
 | Skill | Responsibility |
 |---|---|
@@ -67,8 +73,9 @@ and swarms may provide roles and dispatch. None is a correctness or lifecycle
 authority.
 
 The `ao` CLI supplies deterministic repository checks and generic read-only or
-record helpers where useful. Semantic validation belongs to the Validate skill,
-not a CLI state machine.
+record helpers where useful. A fresh native reviewer owns semantic validation;
+the optional Validate skill packages that method. A CLI cannot issue semantic
+acceptance from successful checks alone.
 
 ## Sovereign evidence
 
@@ -81,8 +88,9 @@ and ledger availability are never required for validity.
 
 ## Selected Context Delivery Lifecycle contract
 
-The lean [RPI charter](skills/rpi/SKILL.md) owns the authorized outcome through
-finish with on-demand Plan, Implement, Validate and optional Memory. Known
+Native execution owns the authorized outcome through finish. The optional
+[RPI charter](skills/rpi/SKILL.md) supplies on-demand Plan, Implement, Validate
+and Memory when selected. Known
 failures get direct repair; evidence can revise an approach within unchanged
 acceptance and scope. A genuine causal stall admits at most one bounded helper,
 never a helper chain. Cheap checks precede fresh author-distinct final judgment;

PROGRAM.md

@@ -1,19 +1,19 @@
 # Program
 
-This repository self-hosts the lean RPI charter it ships (ADR-0017). PROGRAM is
+This repository defaults to native execution with optional skills (ADR-0017). PROGRAM is
 repository execution guidance, not a product retry or delivery controller.
 
 ## Experiment unit
 
 One invocation consumes and produces:
 
-1. one resolved caller-owned intent, using Plan only when needed and a content
+1. one resolved caller-owned intent, planning only when needed and a content
    snapshot only when necessary;
 2. bounded implementation and checks, with direct repair of known defects and
    evidence-based approach revision within unchanged acceptance;
 3. one runtime-derived subject manifest and factual check receipts with
    complete or honestly incomplete changed-path proof;
-4. fresh author-distinct Validate judgment over exact content, with fresh
+4. fresh author-distinct native judgment over exact content, with fresh
    re-validation after acceptance-relevant repairs;
 5. a subject-led report, with a durable verdict only when requested or required
    by a declared consumer.
@@ -39,7 +39,7 @@ ordinary implementation authority.
 
 Use the cheapest targeted checks during implementation. Before reporting the
 complete change, run the ordinary deterministic suite appropriate to the final
-surface and obtain one fresh Validate verdict. Record exactly what was checked
+surface and obtain one fresh independent judgment. Record exactly what was checked
 and not checked.
 
 The repository may then commit, push, merge, release, or roll back through its