Mission AAR

Defense After-Action Review — workspace KB learnings condense into a need-to-know, marking-gated AarLearning domain with commander approval-to-promote.

The Mission AAR (After-Action Review) pack demonstrates the org-KB learnings exchange in a defense context. Mission documentation, observational notes, and debrief transcripts are captured in a workspace knowledgebase; on finalization (commander approval), the platform condenses them into AarLearning records — sustain/improve findings with observations and recommendations — that land in a need-to-know, AND-of-markings-gated org domain.

What the pack provisions

What	Detail
`AarLearning` object type	Properties: `title` (string), `sustainOrImprove` (string: `sustain` / `improve`), `observation` (text), `recommendation` (text)
`mission_aar_learnings` governed domain	AND-of-markings access policy (need-to-know), commander `approval` action triggers finalize, `references` links back to mission documents
"Mission After-Action Review" process flow	Final stage `approval` action (commander) with `promoteToOrgKb: true`; `knowledge.promotionTarget` → `mission_aar_learnings` / `AarLearning`

Installing the pack provisions both the governed mission_aar_learnings domain and the Mission After-Action Review process flow. Starting a template instance auto-creates a workspace KB linked to mission_aar_learnings. The full mission-documentation-to-learnings journey works from the download.

Download

mission-aar.scrydon-pack.tar.gz — latest.
scrydon-pack-mission-aar-1.0.0.scrydon-pack.tar.gz — version-pinned.

Install

IT admin, once: open Settings → Platform → Packs, upload mission-aar.scrydon-pack.tar.gz, and click Upload. The AarLearning object type and the org-scoped mission_aar_learnings domain are provisioned immediately, and the Mission After-Action Review process flow is made available org-wide.

Workspace admin: open Marketplace in the agentic sidebar and click Add on Mission After-Action Review to opt this workspace in (per-workspace, not per-environment).

Under Process Flows, find Mission After-Action Review and click Start. Name the instance after the mission (e.g. Op Sandstorm AAR). The platform auto-creates a workspace knowledgebase linked to mission_aar_learnings / AarLearning.

Upload debrief transcripts, commander notes, sensor logs, or any mission documentation into the workspace KB.

Learnings flow — commander approval triggers condense

The bundled Mission After-Action Review template's final stage already has an approval action assigned to the commander persona with promoteToOrgKb: true. Work through the stages and assign the final approval to the mission commander. When the commander approves, finalization is triggered automatically.

The platform gathers all workspace KB pages, DLP-scans the corpus, runs a single LLM pass to extract a discrete set of AarLearning records, and DLP-scans the produced learnings.

Each learning is tagged sustain or improve, carries an observation and a recommendation, and includes references listing the exact mission documents that contributed to it.

The learnings enter the org-KB mutation queue and appear in Settings → Organization → Knowledgebase → Review.

Reviewers with the appropriate markings approve the learnings. The AND-of-markings policy requires all required markings to be held — a reviewer missing any single marking cannot approve those rows.

Approved learnings materialize into mission_aar_learnings.

The Workspace-Admin Promote learnings button is also available during iterative planning and rehearsal phases, before formal process finalization. Both paths call the same platform condense.

Governance at a glance

Policy	Setting
Access policy	AND-of-markings (need-to-know)
Finalize trigger	Commander `approval` action with `promoteToOrgKb: true`
References	Each AarLearning lists the mission documents it was derived from
Re-finalize behavior	Upsert by stable learning key — safe across rehearsals and updates

AND-of-markings is strictly enforced. A reader must hold every required marking to access a row — holding some but not all markings results in the row being hidden, not redacted. Configure markings carefully before materializing classified AAR content.

What's interesting about it

AND-of-markings access. Unlike a single classification cap, AND-of-markings requires the reader to hold every declared security marking simultaneously — more fine-grained than a single classification level.
Commander as finalize gate. The promoteToOrgKb directive on the approval action means the commander's approval IS the finalize trigger — no separate "promote" action is needed and no content is promoted without command authority.
References trace learnings to mission docs. Each AarLearning.references entry links to the workspace KB page (e.g. a debrief transcript or sensor log extract) that contributed to the finding. Reviewers can drill back to the source.
sustainOrImprove categorizes findings. sustain = things that went well and should be repeated; improve = things that should change. This maps directly to standard AAR methodology.

Promoting content — broker client reference and both finalize paths.
Process Flows — knowledge.promotionTarget — how to declare the domain link and promoteToOrgKb in a process flow manifest.
Markings & governed retrieval — AND-of-markings enforcement at retrieval.
AML-KYC Casework example — finance vertical with a 2-reviewer quorum.