agentera 3.0.0-dev.5 → 3.0.0-dev.51

package/bundle/skills/agentera/capability_schema_contract.yaml

@@ -9,13 +9,7 @@
 #   3. Deprecation protocol (deprecated + replaced_by)
 #   4. Directory structure requirements (instruction module, schemas/)
 #   5. Machine-readable validation rules consumed by future contract loaders
-#
-# D65: the per-capability `instructions.md` Markdown file is retired. The
-# behavioral instructions now live at
-# `packages/cli/src/capabilities/<name>/instructions.ts` as a default-exported
-# string constant. The directory requirement below points at the new path;
-# the V1 directory_structure rule's `checks` list and the ARTIFACTS A3 path
-# text follow the same move.
+#   6. Optional trigger-entry intent documentation (TRIGGER_ENRICHMENT)
 
 meta:
   name: capability_schema_contract
@@ -54,9 +48,10 @@ ENTRY_SCHEMA:
       type: string
       required: false
       description: >-
-        Priority of this trigger entry for routing confidence. Used in the
-        five-layer routing model (Decision 42). Valid values: high, medium, low.
+        Advisory relevance-precedence hint a host reads alongside the entry
+        description only after deterministic routing returns semantic_required.
         Required for all TRIGGERS entries.
+        Valid values: high, medium, low.
     deprecated:
       type: boolean
       required: false
@@ -85,7 +80,7 @@ DIRECTORY_REQUIREMENTS:
       TypeScript module that exports the capability's behavioral instructions
       as a default-exported string constant. The runtime loads it via the
       compiled .js path and surfaces the prose through
-      `agentera prime --context <name> --format json`.
+      `npx -y agentera@next prime --context <name> --format json`.
   schemas_directory:
     path: schemas
     type: directory
@@ -141,7 +136,112 @@ FIELD_RULES:
         - high
         - medium
         - low
-      description: Priority of this trigger entry for routing confidence.
+      description: >-
+        Relevance-precedence hint a host reads when ordering capability intent
+        after deterministic abstention. See
+        references/cli/routing-model.md for routing semantics.
+
+TRIGGER_ENRICHMENT:
+  description: >-
+    Optional trigger-entry fields. Every field is OPTIONAL: a triggers.yaml
+    entry that omits all enriched fields remains valid. A host consumes
+    disambiguates_against as semantic-phase intent documentation only after
+    deterministic abstention. patterns,
+    confidence_threshold, borderline_band, and patterns_regex are legacy
+    compatibility fields: they remain shape-validated only and never enter the
+    active semantic trigger model.
+  spec: references/cli/trigger-schema-enrichment.md
+  fields:
+    patterns:
+      type: list_of_strings
+      required: false
+      description: >-
+        Legacy matcher strings retained only so existing trigger files load and
+        validate. They are never matched or returned by the active model.
+    confidence_threshold:
+      type: integer
+      required: false
+      min: 0
+      max: 100
+      description: >-
+        Legacy integer 0-100. Not consumed by the LLM host; retained so
+        triggers.yaml files carrying the field still validate. A non-integer
+        or value outside 0..100 fails V7 validation with the valid range
+        and the offending entry ID.
+    borderline_band:
+      type: integer
+      required: false
+      min: 0
+      max: 100
+      description: >-
+        Legacy integer 0-100. Not consumed by the LLM host; retained so
+        triggers.yaml files carrying the field still validate. A non-integer
+        or value outside 0..100 fails V7 validation.
+    patterns_regex:
+      type: list_of_strings
+      required: false
+      each_must_be_valid_regex: true
+      description: >-
+        Legacy list of regex strings. Not consumed by the LLM host; retained
+        so triggers.yaml files carrying the field still validate. The loader
+        syntax-validates each entry but never returns a RegExp or matches it.
+    disambiguates_against:
+      type: list_of_mappings
+      required: false
+      description: >-
+        Declares which other capabilities this trigger's intent could be
+        confused with, with a hint the LLM host consults when a request could
+        match more than one capability (spec §1.2). Advisory: the LLM host
+        resolves ambiguity natively and MAY surface the hint when asking the
+        user to confirm or clarify. Each entry MUST be a mapping with
+        `capability` and `hint`.
+      entries:
+        capability:
+          type: string
+          required: true
+          enum_source: ROUTE_ALIASES.primary_aliases.capability
+          description: >-
+            Canonical capability ID. Must be one of the twelve English
+            canonical IDs enumerated by ROUTE_ALIASES.primary_aliases
+            (status, vision, discuss, research, plan, build, optimize, audit,
+            document, profile, design, orchestrate). A non-canonical value
+            fails V7 validation with the offending entry ID.
+        hint:
+          type: string
+          required: true
+          non_empty: true
+          description: >-
+            Non-empty string distinguishing this trigger's intent from the
+            named capability on near-equal requests. A missing or empty hint
+            fails V7 validation.
+
+PROSE_CONVENTIONS:
+  description: >-
+    Authoring rules for capability behavioral instructions. These
+    conventions govern the prose in
+    packages/cli/src/capabilities/<name>/instructions.ts.
+  modal_vocabulary:
+    authority: RFC 2119
+    keywords:
+      - MUST
+      - MUST NOT
+      - SHOULD
+      - SHOULD NOT
+      - MAY
+    rule: >-
+      Capitalized keywords carry protocol force. Lowercase modal verbs
+      (should, must, may) remain ordinary English with no protocol force.
+      Use capitalized keywords when stating hard requirements, strong
+      recommendations, or optional behavior. Use lowercase modals in
+      natural prose that does not bind the agent.
+    rationale: >-
+      Weak models read capability instructions literally as user commands.
+      Deliberate modal vocabulary disambiguates intent: a capitalized MUST
+      signals a hard constraint, while lowercase "should" in descriptive
+      prose does not bind. This is the disambiguator, not the offender.
+    example: >-
+      Steps SHOULD be ordered by value/effort ratio. Each matrix cell
+      MUST be ≤15 words. A concept MAY reference external sources.
 
 PRIMITIVE_REFERENCE_FIELDS:
   description: >-
@@ -172,41 +272,68 @@ PRIMITIVE_REFERENCE_FIELDS:
 
 ROUTE_ALIASES:
   description: >-
-    Primary plain slash-route aliases from Decision 43. These aliases are exact
-    `/agentera <alias>` routes for users; the Swedish -era capability directory
-    names remain canonical protocol identity. Alias routes are not CLI commands.
+    Primary `/agentera <alias>` slash-route aliases for each capability.
+    English capability names are canonical protocol identity; the route alias
+    word is the canonical ID itself. Swedish -era names are legacy v2-stable
+    references, preserved for the v2 stable distribution and historical
+    artifacts (see legacy_aliases). Alias routes are not CLI commands.
   route_prefix: /agentera
   canonical_name_precedence: true
   cli_boundary: >-
     Slash routes and state commands are distinct: `/agentera plan` routes to
-    planera, while `agentera plan` remains the state-oriented CLI command for
-    reading plan state. Do not add non-hej capability or alias commands to the
-    CLI.
+    the plan capability, while `agentera state plan list` remains the
+    state-oriented CLI command for reading plan state. Do not add capability or
+    alias commands to the CLI.
   primary_aliases:
     - alias: status
-      capability: hej
+      capability: status
     - alias: vision
-      capability: visionera
+      capability: vision
     - alias: discuss
-      capability: resonera
+      capability: discuss
     - alias: research
-      capability: inspirera
+      capability: research
     - alias: plan
-      capability: planera
+      capability: plan
     - alias: build
-      capability: realisera
+      capability: build
     - alias: optimize
-      capability: optimera
+      capability: optimize
     - alias: audit
-      capability: inspektera
+      capability: audit
     - alias: document
-      capability: dokumentera
+      capability: document
     - alias: profile
-      capability: profilera
+      capability: profile
     - alias: design
-      capability: visualisera
+      capability: design
     - alias: orchestrate
-      capability: orkestrera
+      capability: orchestrate
+  legacy_aliases:
+    - legacy: hej
+      canonical: status
+    - legacy: visionera
+      canonical: vision
+    - legacy: resonera
+      canonical: discuss
+    - legacy: inspirera
+      canonical: research
+    - legacy: planera
+      canonical: plan
+    - legacy: realisera
+      canonical: build
+    - legacy: optimera
+      canonical: optimize
+    - legacy: inspektera
+      canonical: audit
+    - legacy: dokumentera
+      canonical: document
+    - legacy: profilera
+      canonical: profile
+    - legacy: visualisera
+      canonical: design
+    - legacy: orkestrera
+      canonical: orchestrate
 
 # ---------------------------------------------------------------------------
 # The four required groups follow. The contract IS a valid capability schema,
@@ -282,9 +409,7 @@ ARTIFACTS:
       Behavioral instructions the agent reads. TypeScript module that exports
       a default-exported string constant. The runtime loads it via the
       compiled .js path and serves the prose through
-      `agentera prime --context <name> --format json`. The Markdown
-      `instructions.md` file is no longer part of the on-disk capability
-      surface (D65).
+      `npx -y agentera@next prime --context <name> --format json`.
     produces: false
     consumes: true
   4:
@@ -365,6 +490,25 @@ VALIDATION:
       - "Contract file contains all required groups"
       - "Contract file entries follow entry schema structure"
       - "Contract file passes deprecation consistency check"
+  7:
+    id: V7
+    rule: trigger_enrichment_fields
+    description: >-
+      Trigger entries MAY carry the optional intent-documentation fields
+      defined in TRIGGER_ENRICHMENT. Enrichment is opt-in per entry;
+      triggers omitting every enriched field remain valid. patterns,
+      confidence_threshold, borderline_band, and patterns_regex are legacy
+      compatibility fields only; disambiguates_against is consumed by the
+      LLM host at runtime. Validating an entry with enriched fields fails
+      when the rules below are violated.
+    severity: error
+    checks:
+      - "patterns, when present, is a list of strings"
+      - "confidence_threshold, when present, is an integer in 0..100"
+      - "borderline_band, when present, is an integer in 0..100"
+      - "patterns_regex entries are strings that compile as regular expressions"
+      - "disambiguates_against entries are mappings with a non-empty hint"
+      - "disambiguates_against.capability is one of the twelve canonical capability IDs"
 
 EXIT_CONDITIONS:
   1:
@@ -378,8 +522,8 @@ EXIT_CONDITIONS:
     id: E2
     condition: invalid_structure
     description: >-
-      Directory structure validation failed. Missing instructions.md, schemas/
-      directory, or YAML files.
+      Directory structure validation failed. Missing instruction module,
+      schemas/ directory, or YAML files.
     exit_code: 1
   3:
     id: E3

package/bundle/skills/agentera/protocol.yaml

@@ -59,18 +59,18 @@
 #   Structural: inline separator (·)               → VISUAL_TOKENS.16    (VT16)
 #   Structural: flow/target (→)                    → VISUAL_TOKENS.17    (VT17)
 #   Structural: progress bar (█▓░)                 → VISUAL_TOKENS.18    (VT18)
-#   Skill glyph: hej (⌂)                           → SKILL_GLYPHS.1      (SG1)
-#   Skill glyph: realisera (⧉)                     → SKILL_GLYPHS.2      (SG2)
-#   Skill glyph: inspektera (⛶)                    → SKILL_GLYPHS.3      (SG3)
-#   Skill glyph: resonera (❈)                      → SKILL_GLYPHS.4      (SG4)
-#   Skill glyph: planera (≡)                       → SKILL_GLYPHS.5      (SG5)
-#   Skill glyph: visionera (⛥)                     → SKILL_GLYPHS.6      (SG6)
-#   Skill glyph: optimera (⎘)                      → SKILL_GLYPHS.7      (SG7)
-#   Skill glyph: dokumentera (▤)                   → SKILL_GLYPHS.8      (SG8)
-#   Skill glyph: profilera (♾)                     → SKILL_GLYPHS.9      (SG9)
-#   Skill glyph: inspirera (⬚)                     → SKILL_GLYPHS.10     (SG10)
-#   Skill glyph: visualisera (◰)                   → SKILL_GLYPHS.11     (SG11)
-#   Skill glyph: orkestrera (⎈)                    → SKILL_GLYPHS.12     (SG12)
+#   Skill glyph: status (⌂)                          → SKILL_GLYPHS.1      (SG1)
+#   Skill glyph: build (⧉)                           → SKILL_GLYPHS.2      (SG2)
+#   Skill glyph: audit (⛶)                          → SKILL_GLYPHS.3      (SG3)
+#   Skill glyph: discuss (❈)                         → SKILL_GLYPHS.4      (SG4)
+#   Skill glyph: plan (≡)                            → SKILL_GLYPHS.5      (SG5)
+#   Skill glyph: vision (⛥)                          → SKILL_GLYPHS.6      (SG6)
+#   Skill glyph: optimize (⎘)                        → SKILL_GLYPHS.7      (SG7)
+#   Skill glyph: document (▤)                        → SKILL_GLYPHS.8      (SG8)
+#   Skill glyph: profile (♾)                         → SKILL_GLYPHS.9      (SG9)
+#   Skill glyph: research (⬚)                        → SKILL_GLYPHS.10     (SG10)
+#   Skill glyph: design (◰)                          → SKILL_GLYPHS.11     (SG11)
+#   Skill glyph: orchestrate (⎈)                     → SKILL_GLYPHS.12     (SG12)
 #
 # SPEC Section 18 (Phase Tracking):
 #   Phase: envision                                → PHASES.1            (PH1)
@@ -349,73 +349,73 @@ VISUAL_TOKENS:
 SKILL_GLYPHS:
   1:
     id: SG1
-    capability: hej
+    capability: status
     glyph: "\u2302"
     glyph_code: U+2302
     meaning: "home base"
   2:
     id: SG2
-    capability: realisera
+    capability: build
     glyph: "\u29C9"
     glyph_code: U+29C9
     meaning: "joined building blocks"
   3:
     id: SG3
-    capability: inspektera
+    capability: audit
     glyph: "\u26F6"
     glyph_code: U+26F6
     meaning: "viewfinder frame"
   4:
     id: SG4
-    capability: resonera
+    capability: discuss
     glyph: "\u2748"
     glyph_code: U+2748
     meaning: "spark of insight"
   5:
     id: SG5
-    capability: planera
+    capability: plan
     glyph: "\u2261"
     glyph_code: U+2261
     meaning: "structured layers"
   6:
     id: SG6
-    capability: visionera
+    capability: vision
     glyph: "\u26E5"
     glyph_code: U+26E5
     meaning: "guiding star"
   7:
     id: SG7
-    capability: optimera
+    capability: optimize
     glyph: "\u2398"
     glyph_code: U+2398
     meaning: "measurement"
   8:
     id: SG8
-    capability: dokumentera
+    capability: document
     glyph: "\u25A4"
     glyph_code: U+25A4
     meaning: "text on page"
   9:
     id: SG9
-    capability: profilera
+    capability: profile
     glyph: "\u267E"
     glyph_code: U+267E
     meaning: "permanent mark"
   10:
     id: SG10
-    capability: inspirera
+    capability: research
     glyph: "\u2B1A"
     glyph_code: U+2B1A
     meaning: "frame to fill"
   11:
     id: SG11
-    capability: visualisera
+    capability: design
     glyph: "\u25F0"
     glyph_code: U+25F0
     meaning: "design grid"
   12:
     id: SG12
-    capability: orkestrera
+    capability: orchestrate
     glyph: "\u2388"
     glyph_code: U+2388
     meaning: "helm, steering"
@@ -424,7 +424,7 @@ PHASES:
   1:
     id: PH1
     value: envision
-    capabilities: [visionera]
+    capabilities: [vision]
     purpose: "Define or refine the project's north star"
     valid_successors: [deliberate, plan, build]
     terminal: false
@@ -432,15 +432,15 @@ PHASES:
   2:
     id: PH2
     value: deliberate
-    capabilities: [resonera]
-    purpose: "Reason through decisions before committing to a direction"
+    capabilities: [discuss, research]
+    purpose: "Reason through decisions or external evidence before committing to a direction"
     valid_successors: [plan, build, envision]
     terminal: false
     self_transition: false
   3:
     id: PH3
     value: plan
-    capabilities: [planera]
+    capabilities: [plan]
     purpose: "Structure work into tasks with dependencies and acceptance criteria"
     valid_successors: [build, deliberate]
     terminal: false
@@ -448,15 +448,15 @@ PHASES:
   4:
     id: PH4
     value: build
-    capabilities: [realisera, optimera, dokumentera, visualisera]
-    purpose: "Implement, optimize, document, or design"
+    capabilities: [build, optimize, document, profile, design]
+    purpose: "Implement, optimize, document, profile, or design"
     valid_successors: [build, audit, plan]
     terminal: true
     self_transition: true
   5:
     id: PH5
     value: audit
-    capabilities: [inspektera]
+    capabilities: [audit]
     purpose: "Evaluate structural health and alignment"
     valid_successors: [build, plan, deliberate, envision]
     terminal: true

package/bundle/skills/agentera/route-phrases.yaml

@@ -0,0 +1,81 @@
+schema_version: agentera.route_phrase_registry.v1
+status: active_authority
+purpose: >-
+  Own the small, explicit inventory of deterministic leading phrases. Trigger
+  schemas remain semantic intent documentation and are not a phrase source.
+normalization: references/cli/hybrid-route-contract.yaml#phrase_matching
+rules:
+  stable_ids: Phrase IDs are permanent and never reassigned.
+  active_matching: Only entries with status active are eligible for matching.
+  global_collisions: >-
+    Normalized phrases must be unique across active and deprecated entries; a
+    collision is a validation error, never a precedence decision.
+  direct_route_collisions: >-
+    A phrase cannot duplicate or begin with a canonical capability name or a
+    primary alias under the direct-route grammar.
+  deprecation: >-
+    Remove no entry. Mark it deprecated, retain its ID and phrase, and set
+    replaced_by to an active registry ID. Deprecated phrases abstain.
+  prohibited_sources: [legacy_patterns, regexes, thresholds, bands, trigger_descriptions]
+
+phrases:
+  - id: RP_STATUS_PROJECT_BRIEFING
+    capability: status
+    phrase: show project briefing
+    status: active
+    evidence: [DEV-PHRASE-STATUS]
+  - id: RP_VISION_PRODUCT_DIRECTION
+    capability: vision
+    phrase: define product direction
+    status: active
+    evidence: [DEV-PHRASE-VISION]
+  - id: RP_DISCUSS_DECISION
+    capability: discuss
+    phrase: help me decide
+    status: active
+    evidence: [DEV-PHRASE-DISCUSS]
+  - id: RP_RESEARCH_EXTERNAL_PATTERNS
+    capability: research
+    phrase: study external patterns
+    status: active
+    evidence: [DEV-PHRASE-RESEARCH]
+  - id: RP_PLAN_IMPLEMENTATION
+    capability: plan
+    phrase: make an implementation plan
+    status: active
+    evidence: [DEV-PHRASE-PLAN]
+  - id: RP_BUILD_APPROVED_PLAN
+    capability: build
+    phrase: implement the approved plan
+    status: active
+    evidence: [DEV-PHRASE-BUILD]
+  - id: RP_OPTIMIZE_BOTTLENECK
+    capability: optimize
+    phrase: improve a measured bottleneck
+    status: active
+    evidence: [DEV-PHRASE-OPTIMIZE]
+  - id: RP_AUDIT_CODEBASE_HEALTH
+    capability: audit
+    phrase: check codebase health
+    status: active
+    evidence: [DEV-PHRASE-AUDIT]
+  - id: RP_DOCUMENT_PROJECT
+    capability: document
+    phrase: refresh project documentation
+    status: active
+    evidence: [DEV-PHRASE-DOCUMENT]
+  - id: RP_PROFILE_DECISION
+    capability: profile
+    phrase: save a decision profile
+    status: active
+    evidence: [DEV-PHRASE-PROFILE]
+  - id: RP_DESIGN_INTERFACE
+    capability: design
+    phrase: shape the interface
+    status: active
+    evidence: [DEV-PHRASE-DESIGN]
+  - id: RP_ORCHESTRATE_DELIVERY
+    capability: orchestrate
+    phrase: execute the approved plan
+    status: active
+    evidence: [DEV-PHRASE-ORCHESTRATE]

package/bundle/skills/agentera/schemas/artifacts/changelog.yaml

@@ -1,6 +1,6 @@
 # Changelog Artifact Schema
 #
-# Release history maintained by realisera. Tracks versioned releases with
+# Release history maintained by build. Tracks versioned releases with
 # categorized changes (Added, Changed, Fixed, Removed).
 #
 # Note: CHANGELOG.md is a human-facing Markdown artifact. It remains at the
@@ -11,12 +11,12 @@ meta:
   name: changelog
   version: "1.0.0"
   description: >-
-    Release history. Produced by realisera. Consumed by users and agents
+    Release history. Produced by build. Consumed by users and agents
     for version context. Human-facing: remains Markdown at project root.
   artifact_type: human_facing
   path: "CHANGELOG.md"
-  producer: realisera
-  consumers: [hej, all_skills]
+  producer: build
+  consumers: [status, all_skills]
   format: markdown
 
 GROUP_PREFIXES:
@@ -27,6 +27,7 @@ GROUP_PREFIXES:
 BUDGET:
   1:
     id: CB1
+    scope: full_file
     token_budget: 5000
     description: >-
       Maximum tokens for CHANGELOG.md content. Exceeding triggers compaction.

package/bundle/skills/agentera/schemas/artifacts/decisions.yaml

@@ -1,11 +1,12 @@
 # Decisions Artifact Schema
 #
-# Reasoning trail maintained by resonera. Each deliberation session appends
-# one entry. Decisions are referenced by realisera, optimera, and profilera
+# Reasoning trail maintained by discuss. Each deliberation session appends
+# one entry. Decisions are referenced by build, optimize, and profile
 # for context on why choices were made.
 #
-# Structural pattern: UPPER_CASE groups with numbered entries and stable IDs,
-# following capability_schema_contract.yaml and protocol.yaml conventions.
+# The active authority uses writer-owned decision, revision, and satisfaction
+# entity files. The numbered projection model below is retained only as an exact
+# legacy migration input schema; it is not an ordinary post-cutover contract.
 #
 # ── Field-by-field mapping: v1 DECISIONS.md → v2 decisions.yaml ──
 #
@@ -32,16 +33,28 @@ meta:
   name: decisions
   version: "1.0.0"
   description: >-
-    Reasoning trail maintained by resonera. Each deliberation session
-    appends one entry. Decisions are referenced by realisera, optimera,
-    profilera, planera, inspektera, hej, dokumentera, visionera, resonera,
-    and orkestrera for context on why choices were made.
+    Reasoning trail maintained by discuss. Each deliberation session
+    appends one entry. Decisions are referenced by build, optimize,
+    profile, plan, audit, status, document, vision, discuss,
+    and orchestrate for context on why choices were made.
   artifact_type: agent_facing
   path: ".agentera/decisions.yaml"
-  producer: resonera
-  consumers: [dokumentera, hej, inspektera, optimera, orkestrera, planera, profilera, realisera, resonera, visionera]
+  authority: legacy_migration_input_only
+  producer: discuss
+  consumers: [document, status, audit, optimize, orchestrate, plan, profile, build, discuss, vision]
   format: yaml
 
+ENTITY_AUTHORITY:
+  identity_fields: [id, artifact]
+  artifact: decisions
+  boundaries: [decision, decision_revision, decision_satisfaction]
+  retrieval:
+    list: npx -y agentera@next state decisions list --format json
+    get: npx -y agentera@next state decisions get --id ID --format json
+  mutation: npx -y agentera@next state decisions explain --format json
+  direct_file_edits: forbidden
+  legacy_schema_below: migration_input_only
+
 GROUP_PREFIXES:
   BUDGET: DB
   COMPACTION: DX
@@ -69,10 +82,10 @@ BUDGET:
 COMPACTION:
   1:
     id: DX1
-    rule: uniform_10_40_50
+    rule: lossless_projection
     description: >-
-      Growing artifacts follow a uniform 10/40/50 rule: 10 full-detail
-      entries, 40 one-line archive entries, drop beyond 50 total.
+      The 10/40/50 values are current projection defaults, not deletion limits.
+      Numbered archive records remain complete and unlimited.
   2:
     id: DX2
     full_detail:
@@ -93,21 +106,26 @@ COMPACTION:
       the archive section. Compact summaries preserve decision number, date,
       and chosen alternative; structured compact fields preserve outcome and
       explicit feeds_into references when present so CLI downstream references
-      remain non-inferential.
+      remain non-inferential. Entries beyond the summary default are represented
+      by omission metadata while their numbered archive records remain available.
   4:
     id: DX4
-    dropped:
-      threshold: 50
-      action: "Removed entirely"
+    omission:
+      fields: [omitted, omitted_count, omission_reason, retrieval]
+      reason: projection_capacity_or_byte_budget
     description: >-
-      Decisions older than 50 are dropped entirely.
+      Omitted projection detail is never silently deleted or truncated. The
+      numbered archive is the complete historical source and retrieval points
+      use the direct state get contract.
   5:
     id: DX5
-    trigger: "When resonera writes a new decision"
+    trigger: "When discuss writes a new decision"
     description: >-
       Compaction runs when the producing skill writes a new entry.
-      If >10 full-detail entries exist, collapse the oldest to one-line.
-      If >40 one-line entries exist, drop the oldest.
+      If >10 full-detail entries exist and their numbered archives verify,
+      collapse the oldest to one-line. If >40 summary entries exist, omit the
+      oldest from this bounded projection with metadata; never delete its
+      numbered archive record. Unresolved review entries do not block storage.
   6:
     id: DX6
     archive_section: