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

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

@@ -0,0 +1,24 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: todo
+    local_role: produces
+    description: >-
+      Open problems by severity. Research writes actionable findings here
+      (with user confirmation), classifying each by severity per protocol
+      SF1-SF3. Build picks up changes automatically in its next cycle.
+  2:
+    id: A2
+    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: profile
+    local_role: consumes
+    description: >-
+      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

@@ -0,0 +1,16 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Research requests that analyze external sources, repositories, or approaches.
+    priority: high
+  2:
+    id: T2
+    description: Assess an external source's relevance, applicability, or adoption.
+    priority: high
+  3:
+    id: T3
+    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/{inspirera → research}/schemas/validation.yaml

@@ -3,8 +3,8 @@ VALIDATION:
     id: V1
     rule: read_only_target
     description: >-
-      Inspirera MUST NOT modify code in the target project. It analyzes
-      and maps concepts; other capabilities (realisera, optimera)
+      Research MUST NOT modify code in the target project. It analyzes
+      and maps concepts; other capabilities (build, optimize)
       implement changes. The only writes are to TODO.md and VISION.md,
       and only with explicit user confirmation.
     severity: critical

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

@@ -0,0 +1,73 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: vision
+    local_role: consumes
+    description: >-
+      Status reads this for the briefing's project context.
+  2:
+    id: A2
+    artifact: decisions
+    local_role: consumes
+    description: >-
+      Status reads this to identify unresolved decisions requiring follow-up.
+  3:
+    id: A3
+    artifact: plan
+    local_role: consumes
+    description: >-
+      Status reads this to identify the next executable task and plan progress.
+  4:
+    id: A4
+    artifact: progress
+    local_role: consumes
+    description: >-
+      Status reads this for the briefing's "what shipped" context.
+  5:
+    id: A5
+    artifact: todo
+    local_role: consumes
+    description: >-
+      Status reads this to identify high-severity open items for routing.
+  6:
+    id: A6
+    artifact: health
+    local_role: consumes
+    description: >-
+      Status reads this for the health status line and attention items.
+  7:
+    id: A7
+    artifact: objective
+    local_role: consumes
+    description: >-
+      Status reads this to check for active optimization objectives.
+  8:
+    id: A8
+    artifact: experiments
+    local_role: consumes
+    description: >-
+      Status reads this alongside the active optimization target to determine
+      optimization status.
+  9:
+    id: A9
+    artifact: docs
+    local_role: consumes
+    description: >-
+      Status reads this first to resolve project-local artifact mappings before
+      reading other artifacts.
+  10:
+    id: A10
+    artifact: design
+    local_role: consumes
+    description: >-
+      Status reads this for project design status metadata (exists, stale, missing).
+      Suite chrome styling uses protocol.yaml, prime --context capability prose,
+      and v2 app-home DESIGN.md when present — not the host project's design
+      artifact.
+  11:
+    id: A11
+    artifact: profile
+    local_role: consumes
+    description: >-
+      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

@@ -0,0 +1,22 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Explicit status requests and orientation for the current project.
+    priority: high
+  2:
+    id: T2
+    description: Session-start requests seeking orientation before choosing work.
+    priority: high
+  3:
+    id: T3
+    description: Current project state, briefing, attention, or progress requests.
+    priority: medium
+  4:
+    id: T4
+    description: Resume-work and “what's next?” requests with no separate requested outcome.
+    priority: high
+  5:
+    id: T5
+    description: Fallback orientation when no capability fits the request.
+    fallback: true
+    priority: low

package/bundle/skills/agentera/capabilities/{hej → status}/schemas/validation.yaml

@@ -3,8 +3,8 @@ VALIDATION:
     id: V1
     rule: read_only
     description: >-
-      Hej MUST NOT produce or modify any artifacts. It is strictly read-only.
-      All artifacts consumed by hej are produced by other capabilities.
+      Status MUST NOT produce or modify any artifacts. It is strictly read-only.
+      All artifacts consumed by status are produced by other capabilities.
       This rule verifies that no artifact entry has produces: true.
     severity: critical
     checks:
@@ -25,9 +25,9 @@ VALIDATION:
     id: V3
     rule: exit_marker_required
     description: >-
-      Every hej invocation MUST emit an exit marker after the briefing or
+      Every status invocation MUST emit an exit marker after the briefing or
       welcome. The marker uses the canonical glyph ⌂ (SG1) in the format
-      ⌂ hej · <status> where status is one of EX1-EX4.
+      ⌂ status · <status> where status is one of EX1-EX4.
     severity: critical
     checks:
       - "Exit marker present after closing code fence"
@@ -48,7 +48,7 @@ VALIDATION:
     id: V5
     rule: single_clarifying_question
     description: >-
-      If the routing target is unclear, hej MUST ask exactly one clarifying
+      If the routing target is unclear, status MUST ask exactly one clarifying
       question. Compound questions are not allowed.
     severity: critical
     checks:

package/bundle/skills/agentera/capabilities/{visionera → vision}/schemas/artifacts.yaml

@@ -1,57 +1,57 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: vision
+    artifact: vision
     local_role: produces_and_consumes
     description: >-
-      Visionera writes and refines project direction, principles, personas,
+      Vision writes and refines project direction, principles, personas,
       aspirations, and identity.
   2:
     id: A2
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
-      Visionera reads this to detect shifted thinking during refine mode
+      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: >-
-      Visionera reads this during refine mode to understand what has been
+      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: >-
-      Visionera reads this to understand structural realities that
+      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: >-
-      Visionera reads this during refine mode to detect recurring problems
+      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: >-
-      Visionera reads this during codebase exploration to ensure the
+      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: >-
-      Visionera reads this first to resolve project-local artifact mappings
+      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: >-
-      Visionera reads this to calibrate the vision conversation: high-confidence
+      Vision reads this to calibrate the vision conversation: high-confidence
       entries become proposed principles.

package/bundle/skills/agentera/capabilities/{visionera → 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

@@ -0,0 +1,23 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Requests to define or refine the project's vision and direction.
+    priority: high
+  2:
+    id: T2
+    description: Define a new north star, product direction, or desired future.
+    priority: high
+  3:
+    id: T3
+    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"
+  4:
+    id: T4
+    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/{visionera → 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 realisera execution cycle.
-      Vision changes happen only in dedicated visionera 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 realisera cycle"
+      - "Vision artifact not written during build cycle"
   3:
     id: V3
     rule: inspirational_tone
@@ -29,13 +29,13 @@ 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
     description: >-
       When code exists, the codebase exploration step (Step 1) MUST NOT
-      be skipped. Arriving informed distinguishes visionera from a
+      be skipped. Arriving informed distinguishes vision from a
       blank-slate interview.
     severity: critical
     checks:
@@ -46,26 +46,24 @@ VALIDATION:
     description: >-
       The vision MUST be concrete enough to guide autonomous development.
       "Make a great tool" is not a vision. It must include specific
-      direction, principles, and enough detail for planera to derive tasks.
+      direction, principles, and enough detail for plan to derive tasks.
     severity: critical
     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
     description: >-
-      Every visionera invocation MUST emit an exit marker using the
-      canonical glyph ⛥ (SG6) in the format ⛥ visionera · <status>
+      Every vision invocation MUST emit an exit marker using the
+      canonical glyph ⛥ (SG6) in the format ⛥ vision · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks: