agentera 3.0.0-dev.3 → 3.0.0-dev.31

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

@@ -0,0 +1,20 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Structured deliberation about a choice, decision, or tradeoff.
+    priority: high
+  2:
+    id: T2
+    description: Help decide, think through alternatives, or evaluate tradeoffs.
+    priority: high
+  3:
+    id: T3
+    description: Compare competing options before committing to an approach.
+    priority: high
+  4:
+    id: T4
+    description: Explore uncertain scope or approach before committing to implementation.
+    priority: medium
+    disambiguates_against:
+      - capability: plan
+        hint: "discuss explores options before committing; plan structures committed work"

package/bundle/skills/agentera/capabilities/{resonera → discuss}/schemas/validation.yaml

@@ -3,7 +3,7 @@ VALIDATION:
     id: V1
     rule: one_question_per_turn
     description: >-
-      Resonera MUST ask exactly one question per turn. Compound questions
+      Discuss MUST ask exactly one question per turn. Compound questions
       are not allowed. Every question MUST include a Done option.
     severity: critical
     checks:
@@ -13,16 +13,17 @@ VALIDATION:
     id: V2
     rule: user_approval_for_artifact_writes
     description: >-
-      Resonera MUST NOT modify VISION.md, OBJECTIVE.md, or TODO.md without
-      explicit user confirmation. Present drafts and get approval.
+      Discuss MUST NOT modify vision, objective, or todo artifacts (the
+      protected_write_boundaries) without explicit user confirmation. Present
+      drafts and get approval.
     severity: critical
     checks:
-      - "User confirmation obtained before writing to VISION.md, OBJECTIVE.md, or TODO.md"
+      - "User confirmation obtained before writing to vision, objective, or todo artifacts"
   3:
     id: V3
     rule: decision_confidence_required
     description: >-
-      Every DECISIONS.md entry MUST have a Confidence field with one of the
+      Every decision entry MUST have a Confidence field with one of the
       protocol-defined labels: firm (DL1), provisional (DL2), or
       exploratory (DL3).
     severity: critical
@@ -33,7 +34,7 @@ VALIDATION:
     id: V4
     rule: preserved_decision_fields
     description: >-
-      DECISIONS.md entries MUST preserve the canonical top-level fields:
+      Decision entries MUST preserve the canonical top-level fields:
       Question, Context, Alternatives, Choice, Reasoning, Confidence,
       Feeds into. Win conditions stay inside Alternatives bullets.
     severity: critical
@@ -43,7 +44,7 @@ VALIDATION:
     id: V5
     rule: no_implementation
     description: >-
-      Resonera MUST NOT skip to implementation. It deliberates; other
+      Discuss MUST NOT skip to implementation. It deliberates; other
       capabilities build. If the user wants to build, route to the
       appropriate capability.
     severity: critical
@@ -64,7 +65,7 @@ VALIDATION:
     id: V7
     rule: satisfaction_authority_boundary
     description: >-
-      When Resonera touches decision satisfaction, it may capture provisional
+      When Discuss touches decision satisfaction, it may capture provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction unless the
       user explicitly confirms it. Missing, compacted, open, provisional, or
       review-needed satisfaction state remains a caveat and review pressure;

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

@@ -0,0 +1,80 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: docs
+    local_role: produces_and_consumes
+    description: >-
+      Documentation contract with conventions, artifact mapping, and
+      documentation index. Document writes and reads doc root, style
+      conventions, auto-generated doc tracking, project-local artifact mappings,
+      and a status index (current/stale/missing) for tracked docs. During
+      closeout, Document consumes docs state through CLI `closeout_context`;
+      raw reads are diagnostic-only for corruption or CLI-defect investigation.
+  2:
+    id: A2
+    artifact: vision
+    local_role: consumes
+    description: >-
+      Document reads this to understand who the documentation is for
+      and what tone to use.
+  3:
+    id: A3
+    artifact: progress
+    local_role: consumes
+    description: >-
+      Document reads this during explore-and-generate mode to understand
+      recent project context. During closeout, latest progress evidence and
+      verification pointers are consumed through CLI `closeout_context`, then
+      bounded `agentera state progress list --limit 20 --format json` discovery
+       or exact `state progress get --id ID` retrieval. Raw reads are
+      diagnostic-only for corruption or CLI-defect investigation.
+  4:
+    id: A4
+    artifact: decisions
+    local_role: consumes
+    description: >-
+      Document reads this during explore-and-generate mode for project
+      context and decision awareness through bounded `agentera state decisions
+      list --limit 20 --format json` discovery or exact `state decisions get
+       --id ID` retrieval. Raw reads are diagnostic-only for corruption or
+      CLI-defect investigation.
+  5:
+    id: A5
+    artifact: health
+    local_role: consumes
+    description: >-
+      Document reads this to discover documentation gaps surfaced during health
+      audits through bounded `agentera state health list --limit 20 --format
+       json` discovery or exact `state health get --id ID` retrieval. Raw reads
+      are diagnostic-only for corruption or CLI-defect investigation.
+  6:
+    id: A6
+    artifact: todo
+    local_role: produces_and_consumes
+    description: >-
+      Document writes to this when code diverges from docs (per DTC,
+      the code is wrong). Also reads for context during documentation work;
+      closeout blocker state is consumed through CLI `closeout_context` before
+      any diagnostic-only raw TODO read.
+  7:
+    id: A7
+    artifact: design
+    local_role: consumes
+    description: >-
+      Document reads this to respect the declared aesthetic and voice
+      when generating user-facing documentation.
+  8:
+    id: A8
+    artifact: profile
+    local_role: consumes
+    description: >-
+      Document reads this to calibrate documentation style preferences:
+      detail level, tone, format.
+  9:
+    id: A9
+    artifact: changelog
+    local_role: consumes
+    description: >-
+      Document reads this during closeout synchronization through CLI
+      `closeout_context` to preserve the changelog boundary and avoid inventing
+      release, tag, publication, or remote state.

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

@@ -0,0 +1,16 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Create, maintain, or assess project documentation.
+    priority: high
+  2:
+    id: T2
+    description: Write or create project documentation, including README and agent guidance.
+    priority: high
+  3:
+    id: T3
+    description: Update, verify, or audit documentation, including “audit the docs”.
+    priority: high
+    disambiguates_against:
+      - capability: audit
+        hint: "document maintains project docs; audit reviews codebase health"

package/bundle/skills/agentera/capabilities/{dokumentera → document}/schemas/validation.yaml

@@ -73,8 +73,8 @@ VALIDATION:
     id: V8
     rule: exit_marker_required
     description: >-
-      Every dokumentera invocation MUST emit an exit marker using the
-      canonical glyph ▤ (SG8) in the format ▤ dokumentera · <status>
+      Every document invocation MUST emit an exit marker using the
+      canonical glyph ▤ (SG8) in the format ▤ document · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
@@ -85,35 +85,35 @@ VALIDATION:
     id: V9
     rule: closeout_context_first
     description: >-
-      During final synchronization, Dokumentera MUST use `agentera prime
-      --context dokumentera --format json` and its `closeout_context`
-      before reading TODO, docs, changelog, or progress artifacts directly.
-      Complete closeout context is the normal source for mappings, version
-      policy, blockers, boundaries, progress evidence, benchmark evidence,
-      caveats, fallback commands, raw-read policy, and completeness.
+       During final synchronization, Document MUST use `agentera prime
+       --context document --format json` and its `closeout_context`
+       before using bounded state list/get contracts for TODO, docs, changelog,
+       or progress. Raw artifact access is diagnostic-only or a write target.
+        Complete closeout context is the normal source for mappings, version
+        policy, blockers, boundaries, progress evidence, benchmark evidence,
+        caveats, fallback commands, raw-read policy, and completeness.
     severity: critical
     checks:
-      - "Closeout starts from hej capability context"
+      - "Closeout starts from status capability context"
       - "Complete closeout_context is used before raw artifact reads"
       - "Completeness and non-empty evidence flags are preserved"
   10:
     id: V10
     rule: closeout_fallback_before_raw
     description: >-
-      If closeout context is incomplete or caveated, Dokumentera MUST run the
-      listed existing CLI fallback commands before any last-resort raw artifact
-      read. No unsupported capability-name command or new closeout command may
-      be introduced.
+       If closeout context is incomplete or caveated, Document MUST run the
+       listed bounded CLI fallback commands before any diagnostic-only raw
+       artifact read. No unsupported capability-name command or new closeout command may
+        be introduced.
     severity: critical
     checks:
-      - "Listed CLI fallback commands run before raw artifact reads"
-      - "Raw reads are last-resort diagnostics or write targets only"
-      - "No unsupported capability-name command is introduced"
+       - "Listed bounded CLI fallback commands run before diagnostic-only raw reads"
+       - "Raw reads are diagnostic-only or write targets"
   11:
     id: V11
     rule: closeout_caveat_preservation
     description: >-
-      Dokumentera MUST preserve closeout caveats about stale app/profile state,
+      Document MUST preserve closeout caveats about stale app/profile state,
       compacted or missing state, missing benchmark evidence, absent local
       metadata or tags, and unrecorded publication or remote state. Caveats must
       not be hidden, reconstructed, or converted into approval to refresh apps,
@@ -127,7 +127,7 @@ VALIDATION:
     id: V12
     rule: satisfaction_authority_boundary
     description: >-
-      When Dokumentera touches decision satisfaction, it may record provisional
+      When Document touches decision satisfaction, it may record provisional
       satisfaction with evidence but MUST NOT user-confirm satisfaction. Missing,
       compacted, open, provisional, or review-needed satisfaction state remains a
       caveat and review pressure; automation must not reconstruct hidden outcomes

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/artifacts.yaml

@@ -1,16 +1,16 @@
 ARTIFACTS:
   1:
     id: A1
-    artifact_id: objective
+    artifact: objective
     local_role: produces_and_consumes
     description: >-
       Optimization target definition: metric, current value, target, constraints,
-      scope, and measurement approach. Optimera writes this during brainstorm
+      scope, and measurement approach. Optimize writes this during brainstorm
       and reads it every cycle. Written to only during brainstorm, refine, or
       canonical closure.
   2:
     id: A2
-    artifact_id: optimera_harness
+    artifact: optimize_harness
     local_role: produces
     description: >-
       Eval script that measures the metric and outputs structured JSON. Written
@@ -18,52 +18,52 @@ ARTIFACTS:
       Never modified during optimization cycles.
   3:
     id: A3
-    artifact_id: experiments
+    artifact: experiments
     local_role: produces_and_consumes
     description: >-
       Log of every experiment: hypothesis, method, change, metric before/after,
       regression result, status (kept/discarded/error), conclusion, and next
-      suggestion. Optimera appends to this each cycle.
+      suggestion. Optimize appends to this each cycle.
   4:
     id: A4
-    artifact_id: progress
+    artifact: progress
     local_role: consumes
     description: >-
-      Optimera inspects the last 3 entries to detect 3 consecutive failures
+      Optimize inspects the last 3 entries to detect 3 consecutive failures
       before reporting exit status.
   5:
     id: A5
-    artifact_id: todo
+    artifact: todo
     local_role: produces
     description: >-
-      Optimera writes to this when logging a failure pattern after 3
+      Optimize writes to this when logging a failure pattern after 3
       consecutive failures.
   6:
     id: A6
-    artifact_id: decisions
+    artifact: decisions
     local_role: consumes
     description: >-
-      Optimera reads this during Orient for context on prior deliberations
+      Optimize reads this during Orient for context on prior deliberations
       about the optimization objective.
   7:
     id: A7
-    artifact_id: profile
+    artifact: profile
     local_role: consumes
     description: >-
-      Optimera reads this to modulate experiment aggressiveness and constraint
+      Optimize reads this to modulate experiment aggressiveness and constraint
       tolerance based on user preferences.
   8:
     id: A8
-    artifact_id: docs
+    artifact: docs
     local_role: consumes
     description: >-
-      Optimera reads this first to resolve project-local artifact mappings
+      Optimize reads this first to resolve project-local artifact mappings
       before accessing other artifacts.
   9:
     id: A9
-    artifact_id: benchmark_context
+    artifact: benchmark_context
     local_role: consumes
     description: >-
       CLI-provided startup benchmark summary from `agentera prime --context
-      optimera --format json`. Optimera consumes this before any direct
+      optimize --format json`. Optimize consumes this before any direct
       latest-report.json, latest-report.md, or runs.jsonl diagnostic read.

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/exit.yaml

@@ -5,7 +5,7 @@ EXIT_CONDITIONS:
     description: >-
       One experiment completed the full cycle: hypothesis formulated,
       implementation dispatched, regression check passed, metric measured,
-      decision made (kept or discarded), and EXPERIMENTS.md updated.
+      decision made (kept or discarded), and experiments.yaml updated.
     exit_signal: complete
   2:
     id: E2
@@ -20,7 +20,7 @@ EXIT_CONDITIONS:
     id: E3
     condition: stuck
     description: >-
-      Cannot proceed because OBJECTIVE.md is missing and the brainstorm cannot
+      Cannot proceed because objective.yaml is missing and the brainstorm cannot
       be completed without user input, the eval harness is broken and cannot
       be repaired without user approval, or the regression check infrastructure
       is unavailable.

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

@@ -0,0 +1,16 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Improve an existing system against a measurable target.
+    priority: high
+    disambiguates_against:
+      - capability: audit
+        hint: "optimize tunes existing code; audit reviews codebase health"
+  2:
+    id: T2
+    description: Improve a concrete metric such as startup time, latency, coverage, or size.
+    priority: high
+  3:
+    id: T3
+    description: Benchmark, experiment, or iterate toward a measurable objective.
+    priority: medium

package/bundle/skills/agentera/capabilities/{optimera → optimize}/schemas/validation.yaml

@@ -24,17 +24,17 @@ VALIDATION:
     id: V3
     rule: objective_readonly_during_cycle
     description: >-
-      OBJECTIVE.md MUST NOT be modified during a cycle except for canonical
+      objective.yaml MUST NOT be modified during a cycle except for canonical
       closure when the target is met. Other edits only happen during
       brainstorm or refine.
     severity: critical
     checks:
-      - "OBJECTIVE.md only modified for closure during cycle"
+      - "objective.yaml only modified for closure during cycle"
   4:
     id: V4
     rule: one_experiment_per_invocation
     description: >-
-      Each optimera invocation performs exactly one experiment. Multiple
+      Each optimize invocation performs exactly one experiment. Multiple
       experiments require multiple invocations or /loop setup.
     severity: critical
     checks:
@@ -53,8 +53,8 @@ VALIDATION:
     id: V6
     rule: exit_marker_required
     description: >-
-      Every optimera invocation MUST emit an exit marker. The marker uses
-      the canonical glyph ⎘ (SG7) in the format ⎘ optimera · <status>
+      Every optimize invocation MUST emit an exit marker. The marker uses
+      the canonical glyph ⎘ (SG7) in the format ⎘ optimize · <status>
       where status is one of EX1-EX4.
     severity: critical
     checks:
@@ -65,21 +65,21 @@ VALIDATION:
     id: V7
     rule: benchmark_context_first
     description: >-
-      For benchmark-oriented startup, Optimera MUST start from `agentera prime
-      --context optimera --format json` and consume complete
+      For benchmark-oriented startup, Optimize MUST start from `agentera prime
+      --context optimize --format json` and consume complete
       benchmark_context before direct retained benchmark file reads. Direct
       latest-report.json, latest-report.md, or runs.jsonl reads are last-resort
       diagnostics only when the CLI context is incomplete.
     severity: critical
     checks:
-      - "Optimera startup uses benchmark_context before direct retained benchmark files"
+      - "Optimize startup uses benchmark_context before direct retained benchmark files"
       - "Incomplete benchmark_context follows listed CLI fallback and manual refresh guidance"
       - "Direct benchmark file reads are treated as last-resort diagnostics"
   8:
     id: V8
     rule: benchmark_caveat_preservation
     description: >-
-      Benchmark caveats from benchmark_context MUST be preserved when Optimera
+      Benchmark caveats from benchmark_context MUST be preserved when Optimize
       reports measurement evidence. Agents must not hide, upgrade, reconstruct,
       or infer away caveats for manual-only execution, missing local history,
       runtime coverage degradation, missing token estimates, non-comparable

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

@@ -0,0 +1,76 @@
+ARTIFACTS:
+  1:
+    id: A1
+    artifact: plan
+    local_role: produces_and_consumes
+    description: >-
+      Orchestrate consumes plan task queue state through
+      `agentera prime --context orchestrate --format json` before raw
+       artifact access, then updates status (pending -> complete/blocked) only
+       when resolving a task. Superseded tasks are terminal dependency
+       satisfiers and stay out of ready and blocked queues. Failed evaluator results are recorded through the
+      retry-safe typed `record-evaluation` mutation before retry or blocking.
+  2:
+    id: A2
+    artifact: progress
+    local_role: consumes
+    description: >-
+      Orchestrate consumes progress verification state from the returned
+      orchestration context first, then bounded `agentera state progress list
+      --limit 20 --format json` fallback output. Exact detail uses `state
+      progress get --id ID`; raw reads are diagnostic-only for corruption or
+      CLI-defect investigation.
+  3:
+    id: A3
+    artifact: health
+    local_role: produces_and_consumes
+    description: >-
+      For an active plan whose tasks are all terminal, Orchestrate consumes
+      returned health state and delegates a limited staleness closure check.
+      On PASS it publishes one typed `artifact_freshness` health record through
+      `agentera state health append --input PATH --format json` before setting
+      the still-open plan complete. WARN or FAIL leaves the plan open and
+      surfaces the finding. Bounded `agentera state health list --limit 20
+      --format json` and exact `state health get --id ID` are fallback
+      contracts. Raw reads are diagnostic-only for corruption or CLI-defect
+      investigation.
+  4:
+    id: A4
+    artifact: todo
+    local_role: produces
+    description: >-
+      Orchestrate consumes TODO caveats from CLI startup context and writes
+      blocked task logging only when a task exhausts its retry budget.
+  5:
+    id: A5
+    artifact: decisions
+    local_role: consumes
+    description: >-
+      Orchestrate consumes included decision context or bounded
+      `agentera state decisions list --limit 20 --format json` discovery and
+      exact `state decisions get --id ID` retrieval, preserving firm
+      constraints, exploratory uncertainties, and compacted-entry caveats.
+      Raw reads are diagnostic-only for corruption or CLI-defect investigation.
+  6:
+    id: A6
+    artifact: vision
+    local_role: consumes
+    description: >-
+      Orchestrate consumes returned vision state or missing-state caveats during
+      bootstrap when chaining research for vision-gap analysis.
+  7:
+    id: A7
+    artifact: profile
+    local_role: consumes
+    description: >-
+      Orchestrate consumes returned profile status and caveats first for persona
+      context. If missing or stale, it proceeds without refreshing profile
+      state and preserves the caveat.
+  8:
+    id: A8
+    artifact: docs
+    local_role: consumes
+    description: >-
+      Orchestrate uses docs mapping from CLI startup context first to resolve
+      project-local artifact mappings before any diagnostic-only raw artifact
+      read or artifact write.

package/bundle/skills/agentera/capabilities/{orkestrera → orchestrate}/schemas/exit.yaml

@@ -3,8 +3,9 @@ EXIT_CONDITIONS:
     id: E1
     condition: complete
     description: >-
-      All PLAN.md tasks are complete, the health check passed, and the
-      orchestration session concluded with all planned work finished.
+      All plan tasks are complete or validly superseded, the limited post-plan
+      health check passed, its typed health record was published, and the
+      still-open plan was then set complete without invoking archive.
     exit_signal: complete
   2:
     id: E2
@@ -18,7 +19,7 @@ EXIT_CONDITIONS:
     id: E3
     condition: stuck
     description: >-
-      Cannot proceed. PLAN.md has circular dependencies preventing any task
+      Cannot proceed. The plan has circular dependencies preventing any task
       from becoming eligible, no target capabilities are available to
       delegate, or file access prevents reading or updating artifacts.
       The exit marker explains what is blocking progress.
@@ -27,8 +28,9 @@ EXIT_CONDITIONS:
     id: E4
     condition: waiting
     description: >-
-      No PLAN.md exists and the bootstrap chain cannot proceed because
-      VISION.md is absent and the user has not confirmed how to create one,
-      or a dispatched capability returned waiting status requiring user input.
-      The waiting bullet identifies the specific decision needed.
+      No plan exists and the bootstrap chain cannot proceed because the
+      vision artifact is absent and the user has not confirmed how to
+      create one, or a dispatched capability returned waiting status
+      requiring user input. The waiting bullet identifies the specific
+      decision needed.
     exit_signal: waiting

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

@@ -0,0 +1,23 @@
+TRIGGERS:
+  1:
+    id: T1
+    description: Execute an entire plan or coordinate multiple tasks and capabilities.
+    priority: high
+  2:
+    id: T2
+    description: Run every task in a plan or execute a full plan autonomously.
+    priority: high
+    disambiguates_against:
+      - capability: build
+        hint: "orchestrate runs the whole plan autonomously; build executes one development cycle"
+  3:
+    id: T3
+    description: Coordinate multiple tasks or capability handoffs through completion.
+    priority: medium
+  4:
+    id: T4
+    description: Run evaluated, plan-driven development across multiple tasks without manual sequencing.
+    priority: medium
+    disambiguates_against:
+      - capability: build
+        hint: "orchestrate chains multi-cycle execution; build runs a single cycle"