agentera 3.0.0-dev.2 → 3.0.0-dev.21

package/bundle/skills/agentera/capability_schema_contract.yaml

@@ -7,15 +7,18 @@
 #   1. Required groups every capability schema must contain
 #   2. Entry structure within each group (numbered, stable IDs)
 #   3. Deprecation protocol (deprecated + replaced_by)
-#   4. Directory structure requirements (instructions.md, schemas/)
+#   4. Directory structure requirements (instruction module, schemas/)
 #   5. Machine-readable validation rules consumed by future contract loaders
+#   6. Optional trigger-entry intent documentation (TRIGGER_ENRICHMENT)
 
 meta:
   name: capability_schema_contract
   version: "1.0.0"
   description: >-
     Defines what a valid capability schema looks like.
-    A capability directory must contain instructions.md and a schemas/ directory.
+    A capability directory must contain schemas/ and the runtime must
+    resolve the capability's behavioral instructions from the
+    packages/cli/src/capabilities/<name>/instructions.ts module.
     The union of all YAML files in schemas/ must contain all required groups.
   capability_type: contract
   self_referential: true
@@ -45,9 +48,9 @@ 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.
-        Required for all TRIGGERS entries.
+        Advisory relevance-precedence hint the LLM host reads alongside the
+        entry description. Required for all TRIGGERS entries.
+        Valid values: high, medium, low.
     deprecated:
       type: boolean
       required: false
@@ -68,11 +71,15 @@ GROUP_PREFIXES:
   EXIT_CONDITIONS: E
 
 DIRECTORY_REQUIREMENTS:
-  instruction_file:
-    path: instructions.md
+  instruction_module:
+    path: packages/cli/src/capabilities/<name>/instructions.ts
     type: file
     required: true
-    description: Behavioral instructions the agent reads.
+    description: >-
+      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`.
   schemas_directory:
     path: schemas
     type: directory
@@ -128,7 +135,114 @@ FIELD_RULES:
         - high
         - medium
         - low
-      description: Priority of this trigger entry for routing confidence.
+      description: >-
+        Relevance-precedence hint the LLM host reads when ordering
+        candidate capabilities for a request. 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.
+  spec: references/cli/trigger-schema-enrichment.md
+  contract_defaults:
+    # Default values for optional enriched fields.
+    confidence_threshold: 50
+    borderline_band: 15
+  fields:
+    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
+        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
+      default: 15
+      description: >-
+        Optional 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.
+    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
+        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: >-
@@ -159,41 +273,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` 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,
@@ -246,9 +387,9 @@ ARTIFACTS:
     name: capability_directory
     path: "capabilities/<name>/"
     description: >-
-      A valid capability directory. Must contain instructions.md and schemas/.
-      The schemas/ directory holds YAML files whose union covers all required
-      groups.
+      A valid capability directory. Must contain schemas/. The behavioral
+      instructions module lives at
+      packages/cli/src/capabilities/<name>/instructions.ts.
     produces: false
     consumes: true
   2:
@@ -263,11 +404,13 @@ ARTIFACTS:
     consumes: true
   3:
     id: A3
-    name: instruction_file
-    path: "capabilities/<name>/instructions.md"
+    name: instruction_module
+    path: "packages/cli/src/capabilities/<name>/instructions.ts"
     description: >-
-      Behavioral instructions the agent reads. Markdown format. Contains the
-      capability's workflow, personality, interaction rules, and examples.
+      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`.
     produces: false
     consumes: true
   4:
@@ -285,10 +428,12 @@ VALIDATION:
     id: V1
     rule: directory_structure
     description: >-
-      Capability directory must contain instructions.md and schemas/ directory.
+      Capability directory must contain schemas/ and the instruction module
+      packages/cli/src/capabilities/<name>/instructions.ts must exist as a
+      TypeScript source file (the runtime resolves the compiled .js path).
     severity: error
     checks:
-      - "instructions.md is a file"
+      - "instruction_module is a file"
       - "schemas/ is a directory"
       - "schemas/ contains at least one .yaml file"
   2:
@@ -346,6 +491,24 @@ 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.
+      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.
+    severity: error
+    checks:
+      - "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:
@@ -359,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,7 +432,7 @@ PHASES:
   2:
     id: PH2
     value: deliberate
-    capabilities: [resonera]
+    capabilities: [discuss]
     purpose: "Reason through decisions before committing to a direction"
     valid_successors: [plan, build, envision]
     terminal: false
@@ -440,7 +440,7 @@ PHASES:
   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,7 +448,7 @@ PHASES:
   4:
     id: PH4
     value: build
-    capabilities: [realisera, optimera, dokumentera, visualisera]
+    capabilities: [build, optimize, document, design]
     purpose: "Implement, optimize, document, or design"
     valid_successors: [build, audit, plan]
     terminal: true
@@ -456,7 +456,7 @@ PHASES:
   5:
     id: PH5
     value: audit
-    capabilities: [inspektera]
+    capabilities: [audit]
     purpose: "Evaluate structural health and alignment"
     valid_successors: [build, plan, deliberate, envision]
     terminal: true