@aopslabs/aops 0.3.24 → 0.3.25

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/SKILL.md

@@ -21,7 +21,6 @@ this gateway loaded.
 | install/setup, PostgreSQL, auth, server, health, sync, views, client assets | `references/aops-cli-core/SKILL.md` |
 | read-only local dashboard, sprint/task/board views, focused digest | `references/view/SKILL.md` |
 | durable memory, reusable prompts/skills/resources/artifacts, experience | `references/agentspace/SKILL.md` |
-| durable session intent and resume packs | `references/mission/SKILL.md` |
 | boards, tasks, sprints/plans, issues, feedback, reviews, handoffs | `references/projectman/SKILL.md` |
 | versioned documents, sections, links, search, answer, mirrors | `references/docman/SKILL.md` |
 | encrypted coordination rooms, foreground listen, messages, membership | `references/chatv3/SKILL.md` |

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/references/agentspace/SKILL.md

@@ -49,12 +49,6 @@ aops resource create --help
 Hosted prompt/skill truth lives on the server. Local mirrors are read-only
 context. Artifact records are metadata/pointers, not a large binary store.
 
-## Missions and sessions
-
-For durable session intent and resume packs, load `../mission/SKILL.md` rather
-than the full Agentspace guide. For rooms/messages load
-`../chatv3/SKILL.md`; for structured consensus load
-`../discuss/SKILL.md`.
 
 ## Raw discovery fallback
 

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/references/collaborative-work/SKILL.md

@@ -15,7 +15,6 @@ requirement. Select one mode at kickoff and use
 aops sync status --json
 aops view dashboard --style agent
 aops start --task "<task>" --json --out ./aops-start.md
-aops mission resume --id <mission-id> --json
 aops pm board resume --board <slug> --json
 ```
 
@@ -29,7 +28,7 @@ explicitly marked operator-owned, especially agent identities and roles.
 2. Create or identify the Projectman task/plan appropriate to the work size.
 3. Implement one bounded slice.
 4. Run focused validation and read back hosted mutations.
-5. Update status/handoff; keep board/mission open unless closeout was requested.
+5. Update status/handoff; keep the board open unless closeout was requested.
 
 Useful reads:
 

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/references/working-disciplines/SKILL.md

@@ -22,7 +22,7 @@ Transport and method are separate:
 | `solo-pm-loop` | One agent can deliver the bounded work | PM status, focused validation, handoff |
 | `build-review-chat` | Implementation benefits from an independent review | PM review-request/result; chat only wakes |
 | `design-first-consensus` | A material design decision needs independent stances before build | Discuss conclusion linked to plan |
-| `coordinator-loop` | Several delegated slices need explicit coordinator ownership | Mission policy, slice tasks/reviews, integration gate |
+| `coordinator-loop` | Several delegated slices need explicit coordinator ownership | Projectman policy, slice tasks/reviews, integration gate |
 
 Do not choose a heavier discipline solely because multiple tools exist. The
 operator owns agent count, identities, roles, and closeout authority.
@@ -37,11 +37,8 @@ aops start --task "<task>" --mode chat-room \
   --discipline build-review-chat --json --out ./aops-start.md
 ```
 
-Inspect `result.mission.policyJson` and persist it only if a durable mission is
-appropriate:
 
 ```bash
-aops mission create --objective "<objective>" \
   --policy-json '@policy.json' --apply --json
 ```
 
@@ -53,7 +50,7 @@ aops mission create --objective "<objective>" \
 4. Use ChatV3 (`aops chat`) for coordination/wake, Discuss for consensus, and
    Projectman review-request/result for review truth.
 5. Keep scope changes and blockers explicit; do not fabricate peer approval.
-6. Ordinary stop writes status/handoff and keeps mission/board/room open.
+6. Ordinary stop writes status/handoff and keeps board/room open.
 
 ## Discipline-specific minimums
 

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/user-guides/agentspace.md

@@ -6,7 +6,7 @@
 
 Agentspace owns durable agent/operator context and reusable hosted assets:
 memory, synopsis, prompts, skills, resources, artifacts, activity, experience,
-agent profiles, missions, and structured discussion topics.
+agent profiles and structured discussion topics.
 
 It does not own every part of a work session:
 
@@ -30,7 +30,6 @@ Prefer small, token-efficient reads:
 ```bash
 aops mem brief --subject project --json
 aops mem search --q "<decision or constraint>" --limit 10 --json
-aops mission resume --id <mission-id> --json
 aops view digest --task <task-id> --depth shallow
 aops pm review-request list --status open --json
 aops chat session list --json
@@ -157,20 +156,6 @@ materialize `contentHash` in the RR reference. The result must repeat the exact
 same evidence reference. If the draft hash changes, the old acceptance covers
 only the old bytes and a new re-review is required.
 
-## 8 Missions and closeout
-
-Missions preserve objective and policy; Projectman preserves implementation
-state. Ordinary stop writes a bounded handoff and keeps the mission/task/room
-open. Operator-approved closeout verifies:
-
-1. source and PM state are consistent;
-2. requested tests and independent reviews are recorded;
-3. material findings are resolved or explicitly deferred;
-4. the final ChatV3 message points to durable records;
-5. only then are task/mission/room lifecycle states closed as authorized.
-
-Do not archive a room merely because one listener timed out. Do not mark a
-review accepted from a chat message alone.
 
 ## 9 Raw discovery and troubleshooting
 

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/user-guides/aops-cli.md

@@ -1045,7 +1045,6 @@ Sik kullanilan komutlar:
 ```bash
 aops start --mode solo --board <board> --task "<task>" --json --out tmp/start.md
 aops start --mode chat-room --board <board> --discipline build-review-chat --json
-aops start --resume <mission-id> --mode solo --board <board> --json
 aops start --reminder --task "<current task>" --area <area> --limit 3 --json
 ```
 
@@ -1054,41 +1053,13 @@ Ready sonucunda onemli alanlar:
 1. `result.promptRef.path` / `result.promptRef.sha256` - prompt dosyasi ve hash'i.
 2. `result.memoryBrief` - read-only local-cache memory startup pack; `--no-memory-brief` bunu atlar.
 3. `result.sessionGuidance` - layered runtime rules, discipline guardrails, accepted playbooks, ranked experience briefs.
-4. `result.mission.policyJson` - mission create/update icin free-form policy seed.
 
 `start --reminder` full kickoff degildir: soru sormaz, full starter prompt serialize etmez, PM/memory/hosted state yazmaz. Session ortasinda "neredeydik, hangi kurallar/playbook/experience gecerlidir?" sorusuna bounded read-only cevap verir.
 
-## 35 Mission and implementation plan
 
-### 35.1 Overview
-
-#### 35.1.1 Overview
-
-Mission Agentspace-owned session anchor'dir; Projectman task/sprint/RR truth'un yerine gecmez. Implementation-plan ise Projectman sprint facade'idir; plan id sprint id'dir.
-
-```bash
-aops mission create --objective "<objective>" --policy-json '<json>' --apply --json
-aops mission list --summary --json
-aops mission get --id <mission-id> --json
-aops mission update --id <mission-id> --active-plan <sprint-id> --apply --json
-aops mission resume --id <mission-id> --depth light --limit 8 --json
-
-aops plan create --task <task-id> --name "<plan name>" --goal "<goal>" --apply --json
-aops plan get --id <sprint-id> --json
-aops plan update --id <sprint-id> --phases-json '@tmp/phases.json' --apply --json
-```
+## 35 Playbook and experience consult
 
-Kurallar:
-
-1. Mission intent, status, policy ve active plan ref tutar.
-2. Task, sprint phase/microtask, issue, feedback, RR/RRR Projectman'dedir.
-3. Mission resume compact ve token-bounded'dir; raw skeleton icin `mission resume --full` yalniz gerekliyse kullanilir.
-4. `start --resume <mission-id>` starter prompt ile ayni compact mission pack'i birlestirir.
-5. Tek maddelik microtask editleri icin `aops pm utask ...` kullan; plan facade ikinci tablo degildir.
-
-## 36 Playbook and experience consult
-
-### 36.1 Overview
+### 35.1 Overview
 
 #### 36.1.1 Overview
 
@@ -1108,9 +1079,9 @@ aops skill current --id <skill-id> --summary --json
 
 Default experience limit 3, hard max 5'tir. Brief ilgisizse full body okunmaz; ilgiliyse skill/prompt/current summary, memory/experience detail veya doc ladder ile hedefli okunur.
 
-## 37 Checkpoint cadence
+## 36 Checkpoint cadence
 
-### 37.1 Overview
+### 36.1 Overview
 
 #### 37.1.1 Overview
 

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/files/user-guides/working-disciplines.md

@@ -23,7 +23,7 @@ A discipline is:
 - memory cadence
 - plan and slice rhythm
 
-A discipline is role-agnostic. Reusable discipline text names roles such as `implementer`, `reviewer`, `coordinator`, and `operator-approver`; it does not bind concrete agents to those roles. Concrete agent-to-role assignment belongs in mission-specific `mission.policy.roles`.
+A discipline is role-agnostic. Reusable discipline text names roles such as `implementer`, `reviewer`, `coordinator`, and `operator-approver`; it does not bind concrete agents to those roles. Concrete agent-to-role assignment belongs in the session-specific discipline policy.
 
 The four canonical ids are:
 
@@ -32,7 +32,7 @@ The four canonical ids are:
 | `solo-pm-loop` | Single-agent or low-uncertainty work | Projectman, optional RR, memory |
 | `build-review-chat` | Live implementer plus reviewer work | Projectman RR/RRR, ChatV3 wake, memory |
 | `design-first-consensus` | High design uncertainty or irreversible choices | Discuss, operator approval, Projectman |
-| `coordinator-loop` | Operator delegates session management to one coordinator agent directing implementer agents | Mission policy, Projectman RR/RRR, ChatV3 room, memory |
+| `coordinator-loop` | Operator delegates session management to one coordinator agent directing implementer agents | Projectman RR/RRR, ChatV3 room, memory |
 
 `mode` is transport/session shape: `solo`, `solo+async-review`, or `chat-room`.
 `discipline` is the work policy. A chat-room mode usually maps to
@@ -87,111 +87,22 @@ The start pack includes:
 - `method.selected` with `aliasOf: "discipline"`
 - `guardrails[]`
 - `guardrailGroups.execution` and `guardrailGroups.closeout`
-- `policy` and `policyJson` for mission policy seeding
 - `policy.closeout` with explicit closeout command hints
 - apply-required `deferredBindings`
 
-## 3 Mission policy convention
 
-### 3.1 Overview
-
-#### 3.1.1 Overview
-
-Mission policy stays free-form, but AOPS uses this convention. The current
-`aops start --json` seed includes the main policy groups plus the expanded
-selection/orchestration helpers shown below:
-
-```json
-{
-  "discipline": {
-    "id": "build-review-chat",
-    "version": "s1",
-    "enforcement": "advisory",
-    "selectedBy": "operator",
-    "selectedVia": "--discipline",
-    "recommended": "solo-pm-loop",
-    "signals": {
-      "mode": "solo",
-      "agentCount": 1
-    },
-    "rationale": ["explicit discipline flag supplied"]
-  },
-  "signalMapping": {
-    "mode": "transport/session shape",
-    "agentCount": "coordination complexity",
-    "workSize": "planning granularity",
-    "decisionUncertainty": "design-first trigger",
-    "operatorInterface": "delegation trigger for coordinator-loop"
-  },
-  "guardrails": [],
-  "guardrailGroups": {
-    "execution": [],
-    "closeout": []
-  },
-  "closeout": {
-    "required": true,
-    "trigger": "explicit",
-    "guardrailIds": ["closeout-handoff-memory"],
-    "check": {
-      "command": null,
-      "mode": "read-only",
-      "state": "not-shipped-use-owner-readbacks",
-      "statusStates": [
-        "present",
-        "missing",
-        "deferred-with-owner",
-        "not-applicable",
-        "waived-by-operator"
-      ]
-    },
-    "handoff": {
-      "command": "aops pm handoff write --help",
-      "mode": "owner-surface"
-    }
-  },
-  "review": {},
-  "issue": {},
-  "memory": {},
-  "plan": {},
-  "planning": {},
-  "orchestration": {},
-  "vocabBridge": {
-    "mode": { "meaning": "transport/session shape" },
-    "discipline": { "meaning": "policy preset plus guardrails" },
-    "method": { "aliasOf": "discipline" }
-  }
-}
-```
-
-Use `result.mission.policyJson` from `aops start --json` with
-`aops mission create --policy-json` or `aops mission update --policy-json`.
-
-The exact policy is still advisory and free-form. Treat this convention as a
-stable reading/writing shape, not as a strict schema.
-
-`mission.policy.roles` may bind the generic roles for one mission, for example `implementer`, `reviewer`, `coordinator`, and `operator-approver`. A `coordinator-loop` mission typically binds `roles.operator`, `roles.coordinator`, and one or more `roles.implementer` entries; `roles.reviewer` defaults to the coordinator when absent. This binding is mission-local evidence and must not be copied into reusable discipline docs as a fixed Codex/Claude assignment.
+## 3 Guardrail registry
 
-`guardrailGroups.execution` and `guardrailGroups.closeout` are presentation
-groups over the same `guardrails[]` registry. `policy.closeout` is an
-explicit-before-leaving convention: it records required closeout guardrails,
-the required owner readbacks and a Projectman/memory handoff. This Community
-release has no `mission check` or `mission handoff` command, and it never closes
-boards or chat rooms automatically.
-
-## 4 Guardrail registry
-
-### 4.1 Overview
+### 3.1 Overview
 
 #### 4.1.1 Overview
 
 Every guardrail now has a phase:
 
 - `execution`: applies while planning, implementing, reviewing, and committing.
-- `closeout`: applies before leaving a mission/session or handing it to the next run.
+- `closeout`: applies before leaving a session or handing it to the next run.
 
 Empty `evidence` means reviewer-attested/non-auto-checkable in S1/S2. A later
-`mission check --closeout` must not auto-fail those rows; it may report them as
-not-applicable or reviewer-attested. Non-empty evidence names a surface that a
 future read-only check can inspect.
 
 | Guardrail id | Phase | Disciplines | Evidence | Enforcement |
@@ -201,7 +112,7 @@ future read-only check can inspect.
 | `verify-first-initial-stance` | execution | `build-review-chat`, `design-first-consensus` | `chatv3.message` | advisory |
 | `coordinator-independent-research` | execution | `coordinator-loop` | `projectman.kanban-task`, `projectman.sprint` | advisory |
 | `single-operator-interface` | execution | `coordinator-loop` | `chatv3.message` | advisory |
-| `assignment-via-canonical-refs` | execution | `coordinator-loop` | `agentspace.mission`, `projectman.kanban-task`, `projectman.sprint` | advisory |
+| `assignment-via-canonical-refs` | execution | `coordinator-loop` | `projectman.kanban-task`, `projectman.sprint` | advisory |
 | `idle-window-improvement` | execution | `coordinator-loop` | `projectman.issue`, `projectman.feedback` | advisory |
 | `review-request-per-slice` | execution | `build-review-chat`, `coordinator-loop` | `projectman.review-request`, `chatv3.message` | advisory |
 | `verify-in-code` | execution | `build-review-chat`, `coordinator-loop` | empty | advisory |
@@ -220,20 +131,19 @@ future read-only check can inspect.
 | `closeout-pm-status-audit` | closeout | all | `projectman.status.audit`, `projectman.status.reconcile` | soft-preflight |
 | `closeout-triage-open-reviews` | closeout | all | `projectman.review-request` | soft-preflight |
 | `closeout-triage-open-issues` | closeout | all | `projectman.issue` | soft-preflight |
-| `closeout-mission-status-finalized` | closeout | all | `agentspace.mission.status` | soft-preflight |
-| `closeout-resume-readiness` | closeout | all | `agentspace.mission.resume-pack` | soft-preflight |
+| `closeout-resume-readiness` | closeout | all | `agentspace.memory`, `projectman.implementation-plan`, `projectman.handoff` | soft-preflight |
 | `closeout-session-summary` | closeout | all | `agentspace.memory-item` | soft-preflight |
 | `closeout-slice-review-accounted` | closeout | `build-review-chat`, `coordinator-loop` | `projectman.review-request`, `projectman.issue` | soft-preflight |
 | `closeout-commit-scope-recorded` | closeout | `build-review-chat`, `coordinator-loop` | `git.commit`, `projectman.review-request`, `chatv3.message` | soft-preflight |
-| `closeout-assignment-queue-truthful` | closeout | `coordinator-loop` | `agentspace.mission`, `projectman.kanban-task` | soft-preflight |
+| `closeout-assignment-queue-truthful` | closeout | `coordinator-loop` | `projectman.kanban-task` | soft-preflight |
 | `closeout-discuss-output-finalized` | closeout | `design-first-consensus` | `agentspace.discussion-topic.outputs` | soft-preflight |
 | `closeout-decision-carried-to-execution` | closeout | `design-first-consensus` | `projectman.kanban-task`, `projectman.sprint`, `projectman.issue`, `projectman.feedback` | soft-preflight |
 
-### 4.2 Closeout discipline
+### 3.2 Closeout discipline
 
 #### 4.2.1 Overview
 
-Closeout is the explicit before-leaving phase for an active mission/session. It
+Closeout is the explicit before-leaving phase for an active session. It
 is not the same as operator board closeout or leaving a ChatV3 room.
 
 Use handoff when work continues or a future session must resume. Use complete
@@ -247,7 +157,6 @@ All disciplines share this closeout checklist:
 - run `aops pm status audit` for the active task/board before saying work is done; resolve, reconcile, or explicitly defer stale task/sprint status findings with an owner
 - triage open review requests as accepted, linked to follow-up work, or deferred with owner
 - triage open issues as resolved, linked to follow-up work, or deferred with owner
-- leave mission status truthful: active, handoff, completed, blocked, or deferred
 - prove resume readiness from objective, policy, plan, memory, review, issue, and next-action refs
 - record a concise session summary with changed scope and validation evidence
 
@@ -255,7 +164,6 @@ Closeout status values are intentionally descriptive, not hard-fail booleans:
 `present`, `missing`, `deferred-with-owner`, `not-applicable`, and
 `waived-by-operator`.
 
-The current Community CLI does not ship `mission check` or `mission handoff`.
 Use the owner surfaces instead:
 
 ```bash
@@ -267,9 +175,9 @@ aops mem checkpoint --help
 Agents enforce closeout through PM/RR state, memory, review, chat wake refs,
 and honest handoff notes.
 
-## 5 solo-pm-loop
+## 4 solo-pm-loop
 
-### 5.1 Overview
+### 4.1 Overview
 
 #### 5.1.1 Overview
 
@@ -306,13 +214,13 @@ RR/RRR:
 
 Closeout checklist:
 
-- base closeout guardrails only: handoff memory, review/issue triage, mission status, resume readiness, and session summary
+- base closeout guardrails only: handoff memory, review/issue triage, resume readiness, and session summary
 - optional async review is either accepted or deferred with owner
 - next agent can resume from PM sprint/task plus memory without reading the whole chat
 
-## 6 build-review-chat
+## 5 build-review-chat
 
-### 6.1 Overview
+### 5.1 Overview
 
 #### 6.1.1 Overview
 
@@ -336,7 +244,7 @@ Consensus-to-plan binding:
 - when a material consensus exists, the implementer or reviewer proactively asks whether it should become a PM implementation plan
 - the operator approval gate decides whether the consensus is carried into Projectman
 - execution waits until the plan references the consensus and the reviewer accepts the plan review request
-- the reusable recipe stays role-agnostic; the mission policy decides which concrete agent is implementer or reviewer
+- the reusable recipe stays role-agnostic; the discipline policy decides which concrete agent is implementer or reviewer
 
 Verify-first consensus-to-build recipe:
 
@@ -392,9 +300,9 @@ Closeout checklist:
 - unresolved review findings become PM issues before handoff or completion
 - do not close the room or board unless the operator says to close them
 
-## 7 design-first-consensus
+## 6 design-first-consensus
 
-### 7.1 Overview
+### 6.1 Overview
 
 #### 7.1.1 Overview
 
@@ -437,7 +345,7 @@ Consensus-to-plan binding is mandatory for this discipline when implementation f
 - carry the concluded consensus ref into a Projectman task, sprint-backed implementation plan, issue, or feedback record before implementation resumes
 - the implementation plan goal should explain `NE / NICIN / DONE-WHEN` in operator-readable language
 - execution stays blocked until the operator-approved consensus is bound to the plan and the reviewer accepts the plan approval review request
-- concrete agent names stay in mission policy; the reusable discipline names only implementer, reviewer, and operator-approver roles
+- concrete agent names stay in discipline policy; the reusable discipline names only implementer, reviewer, and operator-approver roles
 
 Closeout checklist:
 
@@ -447,9 +355,9 @@ Closeout checklist:
 - unresolved decision work is deferred with owner instead of disappearing into chat
 - handoff memory names the accepted decision and the next execution surface
 
-## 8 coordinator-loop
+## 7 coordinator-loop
 
-### 8.1 Overview
+### 7.1 Overview
 
 #### 8.1.1 Overview
 
@@ -464,19 +372,19 @@ When to use:
 - review authority is delegated: the coordinator (or a bound reviewer) accepts
   slices; the operator is not paged per slice
 
-Roles (generic, bound per mission in `mission.policy.roles`):
+Roles (generic, bound per session):
 
 - `operator`: human intent, priorities, and approvals; speaks only to the
   coordinator.
 - `coordinator`: single operator interface. Researches independently before
-  assigning, authors mission/task/plan records, assigns work with canonical
-  refs, reviews RRs, instructs commits, keeps PM/mission/memory truthful, and
+  assigning, authors task/plan records, assigns work with canonical
+  refs, reviews RRs, instructs commits, keeps PM/memory truthful, and
   uses idle windows for improvement work (docs, skills, tooling) plus
   issue/feedback capture.
 - `implementer` (one or more): executes assigned slices, opens an RR per slice,
   routes questions and decisions to the coordinator (never directly to the
   operator), commits only on coordinator instruction.
-- `reviewer` (optional): defaults to the coordinator; a mission may bind a
+- `reviewer` (optional): defaults to the coordinator; a session may bind a
   separate reviewer.
 
 Role names are open: `master` or `operator-agent` are discouraged aliases for
@@ -494,9 +402,9 @@ Preset:
   implementer file them; the coordinator also files doc/skill gap findings
   discovered during policy checks
 - memory: the coordinator writes kickoff/checkpoint/closeout memory; assignment
-  truth lives in mission/ktask/plan records, not in chat prose
+  truth lives in ktask/plan records, not in chat prose
 - rhythm: operator request -> coordinator independent research (code, PM,
-  docs) -> mission/ktask/plan authoring -> chat assignment with canonical
+  docs) -> ktask/plan authoring -> chat assignment with canonical
   refs -> implementer slices with RRs -> coordinator review and fix loop ->
   instructed pathspec commit -> next task or idle-window improvement work
 
@@ -504,7 +412,6 @@ Expected flow:
 
 ```bash
 # coordinator: durable anchor + role binding
-aops mission create --objective "<program>" \
   --policy-json '{"discipline":"coordinator-loop","roles":{"operator":"<name>","coordinator":"<agent>","implementer":"<agent>"}}' \
   --apply --json
 
@@ -512,9 +419,8 @@ aops mission create --objective "<program>" \
 aops pm ktask create --board <board> --column Doing --title "<task>" --apply --json
 aops plan create --task <task-id> --name "<plan>" --goal "<goal>" \
   --scope-item "S1 ..." --scope-item "S2 ..." --apply --json
-aops mission update --id <mission-id> --active-plan <plan-id> --apply --json
 aops chat send --session <session> --room general \
-  "GOREV ATAMASI: mission <id> / ktask <id> / plan <id> - S1'den basla, slice basina RR" --json
+  "GOREV ATAMASI: ktask <id> / plan <id> - S1'den basla, slice basina RR" --json
 
 # implementer: per slice
 aops pm review-request create --task <task-id> --sprint <plan-id> \
@@ -529,7 +435,7 @@ aops pm review-request result --id <rr-id> --reviewer <coordinator> \
 Free-form session notes:
 
 - multiple independent tasks may be active at once; each gets its own
-  ktask/plan; the mission stays the session anchor and
+  ktask/plan; the plan stays the session anchor and
   `activeImplementationPlanRef` tracks the current focus
 - the coordinator adapts the depth of process to the task: an atomic fix may
   run as a single RR without a plan; multi-slice work gets a sprint-backed plan
@@ -550,21 +456,20 @@ Closeout checklist:
 - base closeout guardrails plus `build-review-chat` items: every slice RR
   accounted for; commit hash, pathspec, and validation evidence recorded
 - assignment queue truthful: every operator request in the session is bound to
-  a mission/ktask/plan record, completed, or explicitly deferred with owner
+  a ktask/plan record, completed, or explicitly deferred with owner
 - coordinator improvement findings are filed as PM issues/feedback, not left in
   chat
 - handoff memory names the active assignments, review states, and the next
   action per implementer
 
-## 9 Owner boundaries
+## 8 Owner boundaries
 
-### 9.1 Overview
+### 8.1 Overview
 
 #### 9.1.1 Overview
 
 | Surface | Owner | Use for |
 | --- | --- | --- |
-| Mission | Agentspace | durable intent and policy |
 | Projectman | Projectman | task, sprint, microtask, issue, review truth |
 | Discuss | Agentspace discuss | material decisions and final stances |
 | Memory | Agentspace memory | durable carry-forward context |
@@ -575,14 +480,3 @@ Closeout checklist:
 Do not hand-edit `.aops/hosted/**` or `.aops/docman/**` as canonical truth.
 Use hosted commands, then refresh mirrors.
 
-## 10 Later: mission check
-
-### 10.1 Overview
-
-#### 10.1.1 Overview
-
-`aops mission check --closeout` is intentionally later. The MVP check must
-be read-only and inspect PM/discuss/memory evidence plus declared closeout
-status. It must not mutate PM, memory, git, boards, or chat rooms. It should not
-hard-fail by default; strict enforcement is opt-in later through
-`policy.discipline.enforcement = "strict"` or a future explicit closeout policy.

package/agent-assets-release/agent-assets/core/{647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09 → bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb}/manifest.json

@@ -3,14 +3,14 @@
   "entryFile": "SKILL.md",
   "files": [
     {
-      "byteLength": 2738,
+      "byteLength": 2662,
       "path": "SKILL.md",
-      "sha256": "44f8e0ffe807195d6890719e1350a630d159ee74f219001d9393d1d9a8d4818b"
+      "sha256": "3bc86f4ea1d38f668f21da75a2c1afc881794a7f0cfecc92cfcb978454931986"
     },
     {
-      "byteLength": 2681,
+      "byteLength": 2445,
       "path": "references/agentspace/SKILL.md",
-      "sha256": "08e33ef035c41beead342202a1f07af4391b1e4ed62cea9a4d79b43e966c7c0f"
+      "sha256": "716643fab92b155780c999819fbc62cb007a77580ce01ef5be4754399fe6a53e"
     },
     {
       "byteLength": 3804,
@@ -23,9 +23,9 @@
       "sha256": "0f45d8fe418f740456e7f448ce472a7f0784a7cd5b01fe4cbc81439ded3c7931"
     },
     {
-      "byteLength": 2869,
+      "byteLength": 2820,
       "path": "references/collaborative-work/SKILL.md",
-      "sha256": "f4d2af3c384368b1adb1308f2c3731b17e6b4074e4ebdfc8c8f061ba2bb01a67"
+      "sha256": "0be52b14657cbb92781576a58cd901ef187872019660055aba37799de788a890"
     },
     {
       "byteLength": 2386,
@@ -37,11 +37,6 @@
       "path": "references/docman/SKILL.md",
       "sha256": "cf48bfa4d94a97a0d2805d5d9dd7a7d0f7430adaf36b9b2fc685465c42cd8cd7"
     },
-    {
-      "byteLength": 1910,
-      "path": "references/mission/SKILL.md",
-      "sha256": "f4ce9c60c3d12ba45e9eaba0069ed9d8936438a15e0ae1974fa8b15a17ae67a1"
-    },
     {
       "byteLength": 3167,
       "path": "references/projectman/SKILL.md",
@@ -58,9 +53,9 @@
       "sha256": "644603a17444374025acf52975dc5df04e1412d69965b210a28b6b5ed203c90b"
     },
     {
-      "byteLength": 3093,
+      "byteLength": 2947,
       "path": "references/working-disciplines/SKILL.md",
-      "sha256": "406c7215917ff68e22c221847c72af9c38dc9ddab6cb0a4beaedd46038bda08d"
+      "sha256": "e4598aadf22e8ee346fa178b01d073ce0d4bf48a82b10c37e6e03c7523327866"
     },
     {
       "byteLength": 3333,
@@ -68,14 +63,14 @@
       "sha256": "12ef09138579d9bfc75a33d51c78bc50d8b34556eb6070af64a8c03d93927f05"
     },
     {
-      "byteLength": 7702,
+      "byteLength": 7018,
       "path": "user-guides/agentspace.md",
-      "sha256": "18924d928b659eb80a7736a104b56b9693cffe91cc4499e739a2a67a0922c519"
+      "sha256": "3d2b9d40bd3a0e07a082cb73443398f538d96ab11af9e755d54214a0a5038c2b"
     },
     {
-      "byteLength": 52016,
+      "byteLength": 50620,
       "path": "user-guides/aops-cli.md",
-      "sha256": "9984693a3bed26654e7beace62f61dc5227306e4c253ca63f8f3582bed6929a4"
+      "sha256": "ce217a436964db8dd898daa6cc7481cbdb551805ed37ab869bd91f1eae4a135a"
     },
     {
       "byteLength": 5564,
@@ -103,13 +98,13 @@
       "sha256": "3959f5c044314be14f368529edffd7adb80bb475b659397c6f4bbec8086c5f28"
     },
     {
-      "byteLength": 27262,
+      "byteLength": 23129,
       "path": "user-guides/working-disciplines.md",
-      "sha256": "c440185924c91755008ce9977c1ab3128994973038e610fe04cad392b14af79b"
+      "sha256": "c8b2297dc9306ca9d1a8b497b11de8d47a89799ab2425e0c40df955b196cc304"
     }
   ],
   "name": "aops",
-  "packageSha256": "647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09",
+  "packageSha256": "bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb",
   "provenance": {
     "expectedDigestSource": "signed-release-manifest",
     "reference": "aops-platform-agent-assets:core",
@@ -117,6 +112,6 @@
   },
   "schemaVersion": 1,
   "standard": "aops-community-core-v1",
-  "version": "0.3.24",
-  "versionId": "community-core-0.3.24"
+  "version": "0.3.25",
+  "versionId": "community-core-0.3.25"
 }

package/agent-assets-release/agent-assets/inventory.json

@@ -6,12 +6,12 @@
   },
   "core": {
     "entryFile": "SKILL.md",
-    "manifestRef": "agent-assets/core/647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09/manifest.json",
+    "manifestRef": "agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/manifest.json",
     "name": "aops",
     "optional": false,
-    "packageSha256": "647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09",
-    "version": "0.3.24",
-    "versionId": "community-core-0.3.24"
+    "packageSha256": "bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb",
+    "version": "0.3.25",
+    "versionId": "community-core-0.3.25"
   },
   "gateway": {
     "byteLength": 621,
@@ -22,7 +22,7 @@
   "kind": "aops-community-agent-assets-inventory-v1",
   "schemaVersion": 1,
   "source": {
-    "commit": "608842f09f9479d542bac1bb6aa5034dd0002fd4",
+    "commit": "84dae261af584dd7bb566c1b5f8aacaa32778f04",
     "repository": "git+https://github.com/eeemzs/aops-platform",
     "root": "apps/aops-cli/assets/agent-assets"
   }

package/agent-assets-release/agent-assets/projection.json

@@ -1,6 +1,6 @@
 {
   "catalogPackageSha256": [],
-  "corePackageSha256": "647c6e84fbc48f9a36945d81660f4d2a5241f58a53a18054365bfc16868b0f09",
+  "corePackageSha256": "bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb",
   "gatewayRef": "agent-assets/gateway/aops/SKILL.md",
   "kind": "aops-community-agent-assets-projection-v1",
   "root": "agent-assets",