agentera 3.0.0-dev.8 → 3.0.0-dev.81

package/bundle/skills/agentera/capability_schema_contract.yaml

@@ -48,8 +48,9 @@ ENTRY_SCHEMA:
       type: string
       required: false
       description: >-
-        Advisory relevance-precedence hint the LLM host reads alongside the
-        entry description. Required for all TRIGGERS entries.
+        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
@@ -79,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
@@ -136,32 +137,34 @@ FIELD_RULES:
         - medium
         - low
       description: >-
-        Relevance-precedence hint the LLM host reads when ordering
-        candidate capabilities for a request. See
+        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 intent-documentation fields. Every field is
-    OPTIONAL: a triggers.yaml entry that omits all enriched fields remains
-    valid. The LLM host consumes description and disambiguates_against at
-    runtime; confidence_threshold, borderline_band, and patterns_regex are
-    retained as shape-validated documentation so triggers.yaml files that
-    carry them still validate.
+    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
-  contract_defaults:
-    # Default values for optional enriched fields.
-    confidence_threshold: 50
-    borderline_band: 15
   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
-      default: 50
       description: >-
-        Optional integer 0-100. Not consumed by the LLM host; retained so
+        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.
@@ -170,25 +173,21 @@ TRIGGER_ENRICHMENT:
       required: false
       min: 0
       max: 100
-      default: 15
       description: >-
-        Optional integer 0-100. Not consumed by the LLM host; retained so
+        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
-      default: []
       each_must_be_valid_regex: true
       description: >-
-        Optional list of regex strings. Not consumed by the LLM host;
-        retained so triggers.yaml files carrying the field still validate.
-        The loader compiles each entry during validation; a compile failure
-        fails V7 validation naming the offending entry and pattern.
+        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
-      default: []
       description: >-
         Declares which other capabilities this trigger's intent could be
         confused with, with a hint the LLM host consults when a request could
@@ -282,7 +281,7 @@ ROUTE_ALIASES:
   canonical_name_precedence: true
   cli_boundary: >-
     Slash routes and state commands are distinct: `/agentera plan` routes to
-    the plan capability, while `agentera state plan` remains the
+    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:
@@ -410,7 +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`.
+      `npx -y agentera@next prime --context <name> --format json`.
     produces: false
     consumes: true
   4:
@@ -497,13 +496,14 @@ VALIDATION:
     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.
-      confidence_threshold, borderline_band, and patterns_regex are
-      retained as shape-validated documentation; disambiguates_against
-      is consumed by the LLM host at runtime. Validating an entry with
-      enriched fields fails when the rules below are violated.
+      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"

package/bundle/skills/agentera/protocol.yaml

@@ -432,8 +432,8 @@ PHASES:
   2:
     id: PH2
     value: deliberate
-    capabilities: [discuss]
-    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
@@ -448,8 +448,8 @@ PHASES:
   4:
     id: PH4
     value: build
-    capabilities: [build, optimize, document, design]
-    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

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

@@ -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

@@ -4,26 +4,8 @@
 # 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.
-#
-# ── Field-by-field mapping: v1 DECISIONS.md → v2 decisions.yaml ──
-#
-# v1 Field                              v2 Field               v2 ID
-# ─────────────────────────────────────────────────────────────────────
-# ## Decision N · date                  DECISION.number        DC1
-# (date from heading)                   DECISION.date          DC2
-# **Question**: <text>                  DECISION.question      DC3
-# **Context**: <text>                   DECISION.context       DC4
-# **Alternatives**: (list)              ALTERNATIVE entry      DA1
-# (named alt, e.g. "[Foo], chosen")     ALTERNATIVE.name       DA2
-# (chosen/rejected status)              ALTERNATIVE.status     DA3
-# **Choice**: <text>                    DECISION.choice        DC5
-# **Reasoning**: <text>                 DECISION.reasoning     DC6
-# **Confidence**: <label>               DECISION.confidence    DC7
-# **Feeds into**: <text>               DECISION.feeds_into     DC8
-# ## Archived Decisions                 (implicit section)     —
-# - Decision N (date): [Choice] — ...  ARCHIVE.summary        DR1
+# The active authority uses writer-owned decision, revision, and satisfaction
+# entity files.
 #
 # Protocol references:
 #   confidence: DL1-DL3 (protocol.yaml DECISION_LABELS)
@@ -38,10 +20,22 @@ meta:
     and orchestrate for context on why choices were made.
   artifact_type: agent_facing
   path: ".agentera/decisions.yaml"
+  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 +63,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 +87,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 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:

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

@@ -27,6 +27,7 @@ GROUP_PREFIXES:
 BUDGET:
   1:
     id: DB1
+    scope: full_file
     token_budget: 2000
     description: >-
       Maximum tokens for DESIGN.md content. Exceeding triggers compaction.

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

@@ -2,42 +2,14 @@
 #
 # Documentation contract maintained by document. Tracks project doc
 # conventions, artifact path overrides, document index with status, coverage
-# metrics, and timestamped audit findings.
+# metrics, and timestamped audit findings. After durable entity cutover only
+# index entries become independent entities; mappings, conventions, coverage,
+# audit/editorial configuration, and other singleton sections retain
+# intentional whole-document authority in docs.yaml.
 #
 # Structural pattern: UPPER_CASE groups with numbered entries and stable IDs,
 # following capability_schema_contract.yaml and protocol.yaml conventions.
 #
-# ── Field-by-field mapping: v1 DOCS.md → v2 docs.yaml ──
-#
-# v1 Field                              v2 Field               v2 ID
-# ─────────────────────────────────────────────────────────────────────
-# <!-- Last audit: date (label) -->      HEADER.last_audit      DH1
-# ## Conventions / doc_root             CONVENTIONS.doc_root   DC1
-# ## Conventions / style                CONVENTIONS.style      DC2
-# ## Conventions / auto_gen             CONVENTIONS.auto_gen   DC3
-# ## Conventions / version_files        CONVENTIONS.version_files DC4
-# ## Conventions / semver_policy        CONVENTIONS.semver_policy DC5
-# ## Artifact Mapping / table row       MAPPING.entry          DM1
-# (Artifact column)                     MAPPING.artifact       DM2
-# (Path column)                         MAPPING.path           DM3
-# (Producers column)                    MAPPING.producers      DM4
-# ## Index / table row                  INDEX.entry            DI1
-# (Document column)                     INDEX.document         DI2
-# (Path column)                         INDEX.path             DI3
-# (Last Updated column)                 INDEX.last_updated     DI4
-# (Status column)                       INDEX.status           DI5
-# ## Coverage / Documented              COVERAGE.documented    DV1
-# ## Coverage / Undocumented            COVERAGE.undocumented  DV2
-# ## Coverage / Stale                   COVERAGE.stale         DV3
-# ## Coverage / Tests                   COVERAGE.tests         DV4
-# ## Audit Log / ### date (label)       AUDIT_LOG.entry        DA1
-# (audit date from heading)             AUDIT_LOG.date         DA2
-# (audit label from heading)            AUDIT_LOG.label        DA3
-# - [finding_type] description          FINDING.type           DF1
-# (severity from context)               FINDING.severity       DF2
-# (description text)                    FINDING.description    DF3
-# (resolution: fixed/deferred)          FINDING.resolution     DF4
-#
 # Protocol references:
 #   visual tokens: VT1 (protocol.yaml VISUAL_TOKENS, status: current)
 #   severity: SF1-SF3 (protocol.yaml SEVERITY_FINDING)
@@ -70,10 +42,10 @@ BUDGET:
   1:
     id: DB1
     scope: full_file
-    max_words: 2000
+    max_words: null
     description: >-
-      Maximum words for the full file. If a write would exceed this
-      budget, compact older audit log entries.
+      No full-file word budget. Historical audit_log entries are immutable;
+      keep the active inventory and coverage sections concise.
 
 HEADER:
   1:
@@ -393,11 +365,3 @@ VALIDATION:
       Index status values should be from the allowed set.
     checks:
       - "Each status is one of: current, stale, missing, intent, generated"
-  4:
-    id: DVL4
-    rule: word_budget
-    severity: advisory
-    description: >-
-      Advisory check. Full file should be <=2000 words.
-    checks:
-      - "Total file word count <= 2000"

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

@@ -2,36 +2,11 @@
 #
 # Experiment log maintained by optimize. Each experiment records hypothesis,
 # method, metric results, kept/discarded status, and conclusions. Lives
-# alongside OBJECTIVE.md in .agentera/optimera/<name>/.
+# alongside OBJECTIVE.md in .agentera/optimize/<name>/.
 #
 # Structural pattern: UPPER_CASE groups with numbered entries and stable IDs,
 # following capability_schema_contract.yaml and protocol.yaml conventions.
 #
-# ── Field-by-field mapping: v1 EXPERIMENTS.md → v2 experiments.yaml ──
-#
-# v1 Field                              v2 Field               v2 ID
-# ─────────────────────────────────────────────────────────────────────
-# ## Experiment N · date · label        EXPERIMENT.number      EX1
-# (date from heading)                   EXPERIMENT.date        EX2
-# (label from heading)                  EXPERIMENT.label       EX3
-# **Hypothesis**: <text>                EXPERIMENT.hypothesis  EX4
-# **Method**: <text>                    EXPERIMENT.method      EX5
-# **Change**: <text>                    EXPERIMENT.change      EX6
-# **Metric**: <text> + tables           EXPERIMENT.metric      EX7
-# **Regression**: <text>                EXPERIMENT.regression  EX8
-# **Status**: kept/discarded/baseline   EXPERIMENT.status      EX9
-# **Conclusion**: <text>                EXPERIMENT.conclusion  EX10
-# **Next**: <text>                      EXPERIMENT.next        EX11
-# **Escalation**: <text>                EXPERIMENT.escalation  EX12
-# **Target progress**: <text>           EXPERIMENT.target_progress EX13
-# **Brainstorm iteration log**          EXPERIMENT.iteration_log EX14
-# ## Closure · date                     CLOSURE.date           EC1
-# **Final value**: <value>              CLOSURE.final_value    EC2
-# **Target**: <target>                  CLOSURE.target         EC3
-# **Reason**: <text>                    CLOSURE.reason         EC4
-# ## Archived Experiments               (implicit section)     —
-# - EXP-N: result summary              ARCHIVE.summary        EA1
-#
 # Protocol references:
 #   status visual tokens: VT1-VT3 (protocol.yaml VISUAL_TOKENS)
 #   trend tokens: VT12-VT13 (protocol.yaml VISUAL_TOKENS)
@@ -41,9 +16,9 @@ meta:
   version: "1.0.0"
   description: >-
     Experiment log for optimize objectives. Produced and consumed by optimize.
-    Lives in .agentera/optimera/<name>/ alongside the objective.
+    Lives in .agentera/optimize/<name>/ alongside the objective.
   artifact_type: agent_facing
-  path: ".agentera/optimera/<name>/experiments.yaml"
+  path: ".agentera/optimize/<name>/experiments.yaml"
   producer: optimize
   consumers: [status, optimize]
   format: yaml
@@ -54,6 +29,8 @@ GROUP_PREFIXES:
   EXPERIMENT: EX
   CLOSURE: EC
   ARCHIVE: EA
+  PUBLICATION: EP
+  RETRIEVAL: ER
   VALIDATION: EV
 
 BUDGET:
@@ -133,6 +110,7 @@ EXPERIMENT:
     validation:
       - "Must be a non-negative integer"
       - "Must be unique across active and archived entries"
+      - "Identity is <objective-id>/experiment:<number>"
   2:
     id: EX2
     field: date
@@ -267,6 +245,94 @@ EXPERIMENT:
       Harness refinement log for baseline experiments. Each entry
       records a run number, issue encountered, and fix applied.
 
+PUBLICATION:
+  1:
+    id: EP1
+    operation: publish
+    command: >-
+      npx -y agentera@next state experiments publish --objective ID [--id ID]
+      --input EXPERIMENT.yaml --format json
+    description: >-
+      The typed state writer is the mutation authority. It validates the
+      objective, identity, caller entry, and canonical entity state before
+      atomically publishing one experiment entity.
+  2:
+    id: EP2
+    identity: bare_ten_letter_id
+    classification: experiments
+    cli_owned_fields: [id, artifact, objective]
+    retry: byte_equivalent_identity_is_idempotent
+    collision: same_identity_with_different_content_fails
+    description: >-
+      Retry never duplicates an experiment. Invalid identity, collisions, and
+      pre-publication failures preserve active and archive projection bytes.
+  3:
+    id: EP3
+    projection: bounded_entity_list
+    durable_archive: not_applicable
+    description: >-
+      Publication validates and durably publishes one immutable canonical
+      experiment entity. Bounded list output never compacts entity records.
+  4:
+    id: EP4
+    classification: legacy_migration_source_provenance
+    archive_path: '.agentera/<objective-root>/<objective>/archive/experiments/<experiment-number>.yaml'
+    canonical_objective_root: optimize
+    readable_legacy_objective_roots: [optimera]
+    envelope_schema: agentera.experimentArchive.v1
+    required_fields:
+      - schemaVersion
+      - stable_id
+      - objective_id
+      - experiment_number
+      - record
+      - record_sha256
+      - provenance
+    provenance_fields: [authority, objective_id, experiment_id, storage_scope, publication_order]
+    retry: byte_equivalent_envelope_is_idempotent
+    collision: same_identity_with_different_bytes_fails
+    description: >-
+      Archive identity binds stable objective and experiment identity to the
+      immutable full record. Legacy projection entries remain readable without
+      fabricating archive history that predates this publication contract.
+  5:
+    id: EP5
+    directory_durability: fsync_each_new_child_parent_before_advancing
+    exact_full_replay: reconstruct_missing_archive_before_success
+    summary_only_replay: never_reconstruct_without_full_detail
+    description: >-
+      First publication durably records every new archive directory entry.
+      Replay may recover only the exact full record still present in the
+      projection; compacted summaries and dropped rows are not fabricated.
+
+RETRIEVAL:
+  1:
+    id: ER1
+    list: >-
+      npx -y agentera@next state experiments list --objective ID [--limit N]
+      [--cursor TOKEN] --format json
+    get: >-
+      npx -y agentera@next state experiments get --id ID --format json
+    description: >-
+      List returns newest-first objective-scoped canonical entities. Get returns
+      one exact entity by bare ID.
+  2:
+    id: ER2
+    cursor: opaque_snapshot_cursor
+    cursor_binding: [collection, objective, order, snapshot]
+    detail_availability: [full, summary, unavailable]
+    description: >-
+      Cursor tokens are copied, never parsed or constructed. List and get retain
+      compatibility and provenance when legacy detail is summary-only or absent.
+  3:
+    id: ER3
+    maximum_limit: 100
+    max_serialized_utf8_bytes: 32768
+    omission_fields: [omitted, omitted_count, omission_reason, retrieval]
+    description: >-
+      Structured pages omit whole entries rather than truncating scalar values;
+      every addressable omission has continuation or exact-get recovery.
+
 CLOSURE:
   1:
     id: EC1
@@ -317,22 +383,22 @@ ARCHIVE:
 VALIDATION:
   1:
     id: EV1
-    rule: unique_experiment_numbers
+    rule: unique_entity_ids
     severity: error
     description: >-
-      Experiment numbers must be unique and sequential.
+      Experiment IDs must be unique project-wide and match the canonical pattern.
     checks:
-      - "All experiment numbers are unique across active and archived entries"
-      - "Experiment numbers are sequential starting from 0"
+      - "All experiment IDs are unique across canonical entities"
+      - "Every ID is ten lowercase letters"
   2:
     id: EV2
     rule: required_fields
     severity: error
     description: >-
-      Each full-detail experiment entry must have: number, date, label,
+      Each full-detail experiment entity record must have: date, label,
       hypothesis, method, change, metric, status, and conclusion.
     checks:
-      - "number is present and is a non-negative integer"
+      - "the envelope has id and artifact fields"
       - "date is present and matches YYYY-MM-DD HH:MM"
       - "label is present and non-empty"
       - "hypothesis is present and non-empty"
@@ -371,3 +437,43 @@ VALIDATION:
       and serve as the reference measurement.
     checks:
       - "Experiment 0 has status 'baseline'"
+  6:
+    id: EV6
+    rule: identity_compatibility
+    severity: error
+    description: >-
+      Experiment identity is objective-scoped. Reads retain legacy entries with
+      missing or duplicate numbers as unaddressable data with explicit caveats;
+      a new publication must reject ambiguous objective or experiment identity
+      before changing objective, experiment, or archive bytes.
+    checks:
+      - "Objective identity is stable across title and directory rename"
+      - "Experiment 0 and later non-negative numbers are addressable"
+      - "Duplicate or missing experiment numbers remain visible but unaddressable"
+      - "Publication rejects ambiguity before effects"
+  7:
+    id: EV7
+    rule: validated_publication
+    severity: error
+    description: >-
+      New experiments are published only through the typed writer after pure
+      identity and schema preflight, with atomic replacement and idempotent retry.
+    checks:
+      - "Caller input omits the CLI-owned number field"
+      - "Objective and experiment identity validate before staging"
+      - "Final experiments.yaml bytes validate before atomic replacement"
+      - "A byte-equivalent retry returns the existing experiment without duplication"
+  8:
+    id: EV8
+    rule: durable_archive_before_projection
+    severity: error
+    description: >-
+      Newly published full detail must be validated, immutably archived, and
+      directory-synced before the compacted projection is replaced.
+    checks:
+      - "Archive envelope identity and provenance validate before publication"
+      - "Every newly created archive directory entry is parent-synced in order"
+      - "Archive publication succeeds before projection replacement"
+      - "Exact full replay reconstructs a missing archive before success"
+      - "Conflicting immutable archive bytes preserve archive and projection"
+      - "Retry after archive or projection interruption does not duplicate detail"