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

package/bundle/skills/agentera/capabilities/profile/schemas/triggers.yaml

@@ -1,49 +1,20 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests profile.
+    description: Create, maintain, or analyze a reusable decision profile.
     priority: high
-    patterns:
-      - "profile"
-      - "/profile"
-    confidence_threshold: 55
   2:
     id: T2
-    description: >-
-      Profile generation requests. Matches when the user wants to build
-      or regenerate their decision profile from scratch.
-    priority: medium
-    patterns:
-      - "build decision profile"
-      - "generate decision profile"
-      - "rebuild my profile"
-      - "regenerate profile"
-    confidence_threshold: 45
+    description: Build, generate, or regenerate a decision profile.
+    priority: high
+    disambiguates_against:
+      - capability: build
+        hint: "profile builds a reusable decision profile; build implements a software task"
   3:
     id: T3
-    description: >-
-      Profile maintenance requests. Matches when the user wants to update,
-      validate, or check their existing profile.
+    description: Update, validate, or refresh an existing decision profile.
     priority: medium
-    patterns:
-      - "update my profile"
-      - "refresh my decision profile"
-      - "validate my profile"
-      - "check my profile"
-      - "quick profile check"
-    confidence_threshold: 45
   4:
     id: T4
-    description: >-
-      Decision analysis requests. Matches when the user wants to understand
-      their own decision-making patterns or review past decisions.
+    description: Analyze personal decision patterns or review decision history.
     priority: medium
-    patterns:
-      - "what would I decide"
-      - "analyze my decisions"
-      - "mine my sessions"
-      - "decision patterns"
-      - "review my decision history"
-    confidence_threshold: 45

package/bundle/skills/agentera/capabilities/profile/schemas/validation.yaml

@@ -5,11 +5,15 @@ VALIDATION:
     description: >-
       Every profile entry MUST be grounded in observed evidence from session
       history, memory files, configs, or conversation data. Fabricated
-      decision patterns are never acceptable.
+      decision patterns are never acceptable. Synthesis reads the bounded
+      signal tier; a claim's source identity is verified by resolving its
+      evidence_anchor to a retained full-evidence shard rather than re-scanning
+      unbounded history.
     severity: critical
     checks:
       - "Each profile entry traces to a source record"
       - "No profile entry is fabricated without evidence"
+      - "Each claim's evidence_anchor resolves to a retained full-evidence shard"
   2:
     id: V2
     rule: confidence_calibration
@@ -17,11 +21,13 @@ VALIDATION:
       Confidence scores MUST match the evidence tier (protocol CS1-CS5).
       A single data point is 30-49 (CS4), not 70+. Bias check: confidence
       is earned through evidence, not assigned by how insightful the
-      decision sounds.
+      decision sounds. When bounded_signals.sufficiency is insufficient,
+      affected categories are capped to CS4 (30-49) or below.
     severity: critical
     checks:
       - "Confidence values fall within protocol tier boundaries"
       - "Single-source entries are capped at CS4 (30-49)"
+      - "Insufficient families cap affected categories to CS4 or below"
   3:
     id: V3
     rule: tension_honesty
@@ -39,11 +45,17 @@ VALIDATION:
     description: >-
       Profile MUST NOT modify session history, memory files, or config
       files. It reads these sources for extraction but never writes to them.
-      The only artifact profile produces is PROFILE.md.
+      The only artifact profile produces is PROFILE.md. Profile MUST NOT
+      load the monolithic corpus.json whole: synthesis reads the bounded
+      signal tier and retrieves full evidence one shard at a time via
+      evidence_anchor. Legacy/missing tiers require a refresh to publish
+      bounded tiers first, never a whole-corpus load.
     severity: critical
     checks:
       - "No writes to session history files"
       - "No writes to memory or config files"
+      - "Monolithic corpus.json is never loaded whole"
+      - "Full-evidence records are retrieved one shard at a time"
   5:
     id: V5
     rule: prediction_accuracy
@@ -55,3 +67,55 @@ VALIDATION:
     checks:
       - "5 predictions tested against held-out prompts"
       - "Accuracy below 3/5 is flagged in profile header"
+  6:
+    id: V6
+    rule: bounded_signal_sufficiency
+    description: >-
+      Profile synthesis MUST consume the bounded signal tier published by
+      extraction, not all full evidence. The sufficiency gate reports
+      underrepresented source families with their retained and intended
+      counts and surfaces the limitation in the profile output and exit
+      signal rather than silently reducing confidence. Sufficiency is
+      assessed per family against the contract minimum_family_retention
+      threshold; a family with zero intended signals is not a violation.
+    severity: warning
+    checks:
+      - "Signal tier state, count, and sufficiency are read before synthesizing"
+      - "Underrepresented families are surfaced with retained and intended counts"
+      - "No high-confidence claims are fabricated from sparse or missing evidence"
+  7:
+    id: V7
+    rule: personal_glossary_output
+    description: >-
+      After writing the base profile, Profile Full MUST consume only one existing
+      consent-bound user-local generation. The canonical publication operation
+      may render and persist exactly one owned Glossary section only after current
+      decision revalidation, and only for an explicit automatic admission.
+      Entries use only the shared primitive and personal provenance variants.
+      Replacement preserves every non-glossary byte, malformed or ambiguous
+      boundaries fail before effects, and personal production never reads a
+      project glossary.
+    severity: critical
+    checks:
+      - "Explicit publication retains exactly one current user-authored evidence anchor"
+      - "Inferred entries cannot receive automatic publication"
+      - "Non-glossary PROFILE.md bytes and decision-pattern confidence are unchanged"
+      - "No project glossary identity, path, parameter, import, or read is used"
+      - "Missing, failed, empty, degraded, or review-only mining preserves the base and owned section"
+      - "Degraded coverage performs no candidate classification, decision, review queue, or publication"
+  8:
+    id: V8
+    rule: personal_glossary_lifecycle
+    description: >-
+      Established entries MUST survive regeneration without fresh evidence.
+      Confidence is deterministically derived from the retained confidence basis,
+      unchanged permanence class, injected date, existing Profile decay formula,
+      and floor; permanence and observed_at remain unchanged. Matching fresh
+      evidence follows the shared authority refresh rule. Lookup remains deferred.
+    severity: critical
+    checks:
+      - "Same-date replay is idempotent and decay never compounds from rendered confidence"
+      - "Stable, durable, and situational classes use their existing lambdas and floor"
+      - "Fresh evidence refreshes only matching meaning and provenance kind"
+      - "Glossary confidence never mutates decision-pattern confidence"
+      - "Question-capable hosts present only a bounded queued review set; other hosts use the durable queue"

package/bundle/skills/agentera/capabilities/research/schemas/artifacts.yaml

@@ -1,7 +1,7 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: todo
+    artifact: todo
     local_role: produces
     description: >-
       Open problems by severity. Research writes actionable findings here
@@ -9,16 +9,16 @@ ARTIFACTS:
       SF1-SF3. Build picks up changes automatically in its next cycle.
   2:
     id: A2
-    artifact_id: vision
+    artifact: vision
     local_role: produces
     description: >-
       Research may refine project direction with user confirmation when the
       analysis shifts thinking about the project's direction.
   3:
     id: A3
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
-      Research reads this via the effective profile script to weight
-      applicability judgments. If missing, research proceeds without persona
-      grounding.
+      Research reads the profile via research_context.profile from the prime
+      context to weight applicability judgments. If missing, research proceeds
+      without persona grounding.

package/bundle/skills/agentera/capabilities/research/schemas/triggers.yaml

@@ -1,40 +1,16 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests research.
+    description: Research requests that analyze external sources, repositories, or approaches.
     priority: high
-    patterns:
-      - "research"
-      - "/research"
-    confidence_threshold: 55
   2:
     id: T2
-    description: >-
-      Applicability assessment requests. Matches when the user provides
-      an external URL and asks how it applies to their project or whether
-      they should adopt it.
-    priority: medium
-    patterns:
-      - "could I use this in"
-      - "how does this apply to my project"
-      - "is this relevant to"
-      - "what can I take from this"
-      - "should I adopt"
-    confidence_threshold: 45
+    description: Assess an external source's relevance, applicability, or adoption.
+    priority: high
   3:
     id: T3
-    description: >-
-      External resource review requests. Matches when the user wants
-      analysis of a library, repo, or approach for ideas and patterns.
-    priority: medium
-    patterns:
-      - "what do you think of this library"
-      - "review this repo for ideas"
-      - "anything worth stealing from"
-      - "how does this compare to what I'm doing"
-    confidence_threshold: 45
+    description: Review an external library, repository, or pattern for ideas.
+    priority: high
     disambiguates_against:
       - capability: audit
         hint: "research reviews external resources for ideas; audit reviews the local codebase for health"

package/bundle/skills/agentera/capabilities/status/schemas/artifacts.yaml

@@ -1,63 +1,63 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: vision
+    artifact: vision
     local_role: consumes
     description: >-
       Status reads this for the briefing's project context.
   2:
     id: A2
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
       Status reads this to identify unresolved decisions requiring follow-up.
   3:
     id: A3
-    artifact_id: plan
+    artifact: plan
     local_role: consumes
     description: >-
       Status reads this to identify the next executable task and plan progress.
   4:
     id: A4
-    artifact_id: progress
+    artifact: progress
     local_role: consumes
     description: >-
       Status reads this for the briefing's "what shipped" context.
   5:
     id: A5
-    artifact_id: todo
+    artifact: todo
     local_role: consumes
     description: >-
       Status reads this to identify high-severity open items for routing.
   6:
     id: A6
-    artifact_id: health
+    artifact: health
     local_role: consumes
     description: >-
       Status reads this for the health status line and attention items.
   7:
     id: A7
-    artifact_id: objective
+    artifact: objective
     local_role: consumes
     description: >-
       Status reads this to check for active optimization objectives.
   8:
     id: A8
-    artifact_id: experiments
+    artifact: experiments
     local_role: consumes
     description: >-
       Status reads this alongside the active optimization target to determine
       optimization status.
   9:
     id: A9
-    artifact_id: docs
+    artifact: docs
     local_role: consumes
     description: >-
       Status reads this first to resolve project-local artifact mappings before
       reading other artifacts.
   10:
     id: A10
-    artifact_id: design
+    artifact: design
     local_role: consumes
     description: >-
       Status reads this for project design status metadata (exists, stale, missing).
@@ -66,7 +66,8 @@ ARTIFACTS:
       artifact.
   11:
     id: A11
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
-      Status reads this to report profile status (loaded/not found) in the briefing.
+      Status reports profile validity as valid, absent, or repair_needed and
+      keeps freshness separate without exposing profile paths or content.

package/bundle/skills/agentera/capabilities/status/schemas/triggers.yaml

@@ -1,64 +1,22 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests status.
+    description: Explicit status requests and orientation for the current project.
     priority: high
-    patterns:
-      - "status"
-      - "/status"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Greetings and session-start signals. Matches casual greetings or
-      explicit session start requests.
-    priority: medium
-    patterns:
-      - "hello"
-      - "hi"
-      - "start"
-      - "begin"
-      - "getting started"
-      - "onboard me"
-    confidence_threshold: 40
+    description: Session-start requests seeking orientation before choosing work.
+    priority: high
   3:
     id: T3
-    description: >-
-      Status and orientation requests. Matches when the user wants to know
-      the current state of the project or get a briefing.
+    description: Current project state, briefing, attention, or progress requests.
     priority: medium
-    patterns:
-      - "status"
-      - "dashboard"
-      - "pulse"
-      - "brief"
-      - "brief me"
-      - "update me"
-      - "what needs attention"
-    confidence_threshold: 45
   4:
     id: T4
-    description: >-
-      Returning-to-project signals. Matches when the user resumes work
-      on a known project and wants to pick up where they left off.
-    priority: medium
-    patterns:
-      - "where were we"
-      - "catch me up"
-      - "what should I work on"
-      - "what's next"
-    confidence_threshold: 45
+    description: Resume-work and “what's next?” requests with no separate requested outcome.
+    priority: high
   5:
     id: T5
-    description: >-
-      Fallback. Status is the default capability when no other capability's
-      trigger patterns match. This entry documents the fallback behavior
-      defined in the routing layer routing logic.
-    patterns:
-      - "*"
+    description: Fallback orientation when no capability fits the request.
     fallback: true
     priority: low
-    confidence_threshold: 0

package/bundle/skills/agentera/capabilities/vision/schemas/artifacts.yaml

@@ -1,56 +1,56 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: vision
+    artifact: vision
     local_role: produces_and_consumes
     description: >-
       Vision writes and refines project direction, principles, personas,
       aspirations, and identity.
   2:
     id: A2
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
       Vision reads this to detect shifted thinking during refine mode
       and to surface unresolved tensions with the vision.
   3:
     id: A3
-    artifact_id: progress
+    artifact: progress
     local_role: consumes
     description: >-
       Vision reads this during refine mode to understand what has been
       built since the vision was last updated.
   4:
     id: A4
-    artifact_id: health
+    artifact: health
     local_role: consumes
     description: >-
       Vision reads this to understand structural realities that
       constrain or inform the vision.
   5:
     id: A5
-    artifact_id: todo
+    artifact: todo
     local_role: consumes
     description: >-
       Vision reads this during refine mode to detect recurring problems
       that suggest the vision needs adjustment.
   6:
     id: A6
-    artifact_id: design
+    artifact: design
     local_role: consumes
     description: >-
       Vision reads this during codebase exploration to ensure the
       Identity section in project direction coheres with the visual system.
   7:
     id: A7
-    artifact_id: docs
+    artifact: docs
     local_role: consumes
     description: >-
       Vision reads this first to resolve project-local artifact mappings
       before accessing other artifacts.
   8:
     id: A8
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
       Vision reads this to calibrate the vision conversation: high-confidence

package/bundle/skills/agentera/capabilities/vision/schemas/exit.yaml

@@ -3,9 +3,9 @@ EXIT_CONDITIONS:
     id: E1
     condition: complete
     description: >-
-      VISION.md was written (Create/Replace mode) or updated (Refine mode)
-      with explicit user approval. The vision is ambitious, concrete, and
-      structured to sustain autonomous development.
+      The vision artifact was written (Create/Replace mode) or updated
+      (Refine mode) with explicit user approval. The vision is ambitious,
+      concrete, and structured to sustain autonomous development.
     exit_signal: complete
   2:
     id: E2
@@ -14,14 +14,15 @@ EXIT_CONDITIONS:
       The vision was produced but with weaknesses worth surfacing: the user
       settled for a less ambitious or less specific vision than pushed for,
       key sections (personas, principles, direction) are thin due to limited
-      conversation depth, or the vision has unresolved tensions with existing
-      DECISIONS.md entries.
+      conversation depth, or the vision has unresolved tensions with
+      existing decision entries.
     exit_signal: flagged
   3:
     id: E3
     condition: stuck
     description: >-
-      Cannot write VISION.md because the user declined to approve the draft
+      Cannot write the vision artifact because the user declined to approve
+      the draft
       and no actionable revision direction was given, or codebase exploration
       failed in a way that would make the vision unreliable.
     exit_signal: stuck

package/bundle/skills/agentera/capabilities/vision/schemas/triggers.yaml

@@ -1,55 +1,23 @@
 TRIGGERS:
   1:
     id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests vision.
+    description: Requests to define or refine the project's vision and direction.
     priority: high
-    patterns:
-      - "vision"
-      - "/vision"
-    confidence_threshold: 60
-    borderline_band: 10
   2:
     id: T2
-    description: >-
-      Vision creation requests. Matches when the user wants to define or
-      create a project vision or north star direction.
-    priority: medium
-    patterns:
-      - "create a vision"
-      - "write VISION.md"
-      - "define the direction"
-      - "set the north star"
-      - "dream bigger"
-    confidence_threshold: 50
+    description: Define a new north star, product direction, or desired future.
+    priority: high
   3:
     id: T3
-    description: >-
-      Vision refinement requests. Matches when the user wants to evolve
-      or rethink an existing vision.
-    priority: medium
-    patterns:
-      - "rethink the vision"
-      - "refine the vision"
-      - "update VISION.md"
-    confidence_threshold: 50
+    description: Refine, rethink, or update an existing vision or north star.
+    priority: high
     disambiguates_against:
       - capability: build
         hint: "vision refines existing project direction; build implements code"
-    patterns_regex:
-      - "\\brefine\\s+the\\s+vision\\b"
-      - "update\\s+VISION\\.md"
   4:
     id: T4
-    description: >-
-      Project bootstrap. Matches when the user wants to bootstrap a new
-      project identity or define what a project should become.
-    priority: medium
-    patterns:
-      - "bootstrap the project"
-      - "what should this project become"
-    confidence_threshold: 50
+    description: Establish a new project's identity or decide what it should become.
+    priority: high
     disambiguates_against:
       - capability: plan
         hint: "vision defines what a project should become; plan structures the work"

package/bundle/skills/agentera/capabilities/vision/schemas/validation.yaml

@@ -3,8 +3,8 @@ VALIDATION:
     id: V1
     rule: user_approval_required
     description: >-
-      VISION.md MUST NOT be written or modified without explicit user
-      approval. Present drafts and get confirmation before writing.
+      The vision artifact MUST NOT be written or modified without explicit
+      user approval. Present drafts and get confirmation before writing.
       This applies to both Create and Refine modes.
     severity: critical
     checks:
@@ -14,12 +14,12 @@ VALIDATION:
     id: V2
     rule: no_realisera_modification
     description: >-
-      VISION.md MUST NOT be modified during a build execution cycle.
-      Vision changes happen only in dedicated vision sessions. This
-      prevents vision drift during autonomous development.
+      The vision artifact MUST NOT be modified during a build execution
+      cycle. Vision changes happen only in dedicated vision sessions.
+      This prevents vision drift during autonomous development.
     severity: critical
     checks:
-      - "VISION.md not written during build cycle"
+      - "Vision artifact not written during build cycle"
   3:
     id: V3
     rule: inspirational_tone
@@ -29,7 +29,7 @@ VALIDATION:
       should inspire and guide, not specify.
     severity: warning
     checks:
-      - "VISION.md is aspirational, not prescriptive"
+      - "The vision artifact is aspirational, not prescriptive"
   4:
     id: V4
     rule: codebase_exploration_required
@@ -51,15 +51,13 @@ VALIDATION:
     checks:
       - "Vision contains specific direction"
       - "Vision contains actionable principles"
-  6:
-    id: V6
-    rule: principle_brevity
-    description: >-
-      Each principle in VISION.md MUST be ≤20 words. Principles are
-      decision guides, not essays. Brevity forces clarity.
-    severity: warning
-    checks:
-      - "Each principle ≤ 20 words"
+  # V6 (principle_brevity) retired per Decision 81: linter does not enforce word
+  # count on principle descriptions; the live vision artifact violates the limit
+  # intentionally (principles carry rationale, not just labels). The
+  # MUST-state-tradeoff / SHOULD-name-prevention / MUST-NOT-name-implementations
+  # rules in capability instructions and the lint abstraction/filler checks
+  # cover principle quality holistically. ID gap (V6 → V7) preserved to avoid
+  # breaking external references to V7.
   7:
     id: V7
     rule: exit_marker_required