agentera 3.0.0-dev.6 → 3.0.0-dev.69

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

@@ -1,62 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: plan
-    local_role: produces_and_consumes
-    description: >-
-      Active plan with tasks, dependencies, and behavioral acceptance criteria.
-      Planera writes this during the planning session and may read existing
-      plan context before replacing or refining it.
-  2:
-    id: A2
-    artifact_id: plan_archive
-    local_role: produces
-    description: >-
-      Created when a plan is fully
-      executed or explicitly discarded by the user. Preserved for historical
-      reference.
-  3:
-    id: A3
-    artifact_id: vision
-    local_role: consumes
-    description: >-
-      Planera reads this during Orient to understand project direction and
-      align the plan with the vision.
-  4:
-    id: A4
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Planera reads firm (DL1) entries only as hard constraints for planning.
-  5:
-    id: A5
-    artifact_id: todo
-    local_role: consumes
-    description: >-
-      Planera reads this to identify related known
-      issues that the plan should address.
-  6:
-    id: A6
-    artifact_id: health
-    local_role: consumes
-    description: >-
-      Planera reads this to factor structural issues into the plan.
-  7:
-    id: A7
-    artifact_id: progress
-    local_role: consumes
-    description: >-
-      Planera reads this to understand what was built recently.
-  8:
-    id: A8
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Planera reads this to calibrate planning depth and pattern preferences.
-  9:
-    id: A9
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Planera reads this first to resolve project-local artifact mappings and
-      reads the versioning block for version bump task generation.

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

@@ -1,34 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests planera for structured planning.
-    priority: high
-    patterns:
-      - "planera"
-      - "/planera"
-  2:
-    id: T2
-    description: >-
-      Planning requests. Matches when the user wants to create a plan,
-      break work down, or specify requirements before building.
-    priority: medium
-    patterns:
-      - "plan this"
-      - "write a plan"
-      - "break this down"
-      - "decompose this"
-      - "spec this out"
-      - "plan before building"
-  3:
-    id: T3
-    description: >-
-      Architectural planning signals. Matches when the user is asking how
-      to approach building something or when the work is too large for a
-      single development cycle.
-    priority: medium
-    patterns:
-      - "how should we build this"
-      - "multi-step feature"
-      - "this is too big for one cycle"

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

@@ -1,61 +0,0 @@
-VALIDATION:
-  1:
-    id: V1
-    rule: behavioral_acceptance_criteria
-    description: >-
-      All acceptance criteria MUST be behavioral (Given/When/Then format)
-      and MUST NOT reference implementation details (class names, API
-      endpoints, database tables, function names, line numbers).
-    severity: critical
-    checks:
-      - "Acceptance criteria use Given/When/Then format"
-      - "No implementation details in acceptance criteria"
-  2:
-    id: V2
-    rule: max_8_tasks
-    description: >-
-      Full plans MUST NOT exceed 8 tasks. If work requires more, it must
-      be split into sequential plans.
-    severity: critical
-    checks:
-      - "Task count ≤ 8 in full plans"
-  3:
-    id: V3
-    rule: adversarial_review_required
-    description: >-
-      Full plans MUST undergo adversarial review. The critic MUST find at
-      least one issue. "Looks good" is not acceptable. Skip level and
-      light plans are exempt.
-    severity: critical
-    checks:
-      - "Adversarial review ran for full plans"
-  4:
-    id: V4
-    rule: plan_final_state_sync
-    description: >-
-      Every full plan MUST end with a "final state sync" task that depends
-      on all prior tasks. This ensures aggregate plan-level CHANGELOG.md,
-      PROGRESS.md, and TODO.md updates.
-    severity: critical
-    checks:
-      - "Full plan has final state sync task as last task"
-  5:
-    id: V5
-    rule: test_proportionality_target
-    description: >-
-      Tasks that include writing tests MUST have a proportionality target
-      in their acceptance criteria. Default: one pass + one fail per
-      testable unit. Override only with explicit rationale.
-    severity: warning
-    checks:
-      - "Test tasks state proportionality target"
-  6:
-    id: V6
-    rule: skip_level_for_trivial_work
-    description: >-
-      Planera MUST detect skip level for trivial work (single-file change,
-      bug fix, config tweak, < 50 lines) and route directly to /realisera
-      without producing a PLAN.md.
-    severity: critical
-    checks:
-      - "Trivial work routed to /realisera without plan"

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

@@ -1,18 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: profile
-    local_role: produces_and_consumes
-    description: >-
-      Decision profile with per-entry confidence scoring, permanence
-      classification, and temporal metadata. Profilera writes this in both Full
-      and Validate modes, then reads it for validation and update context.
-  2:
-    id: A2
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Profilera treats this as a high-signal source for extraction scripts.
-      Each decision entry captures
-      reasoning, tradeoffs, and confidence, making deliberation sessions
-      one of the richest inputs for decision profile generation.

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

@@ -1,45 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests profilera.
-    priority: high
-    patterns:
-      - "profilera"
-      - "/profilera"
-  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"
-  3:
-    id: T3
-    description: >-
-      Profile maintenance requests. Matches when the user wants to update,
-      validate, or check their existing profile.
-    priority: medium
-    patterns:
-      - "update my profile"
-      - "refresh my decision profile"
-      - "validate my profile"
-      - "check my profile"
-      - "quick profile check"
-  4:
-    id: T4
-    description: >-
-      Decision analysis requests. Matches when the user wants to understand
-      their own decision-making patterns or review past decisions.
-    priority: medium
-    patterns:
-      - "what would I decide"
-      - "analyze my decisions"
-      - "mine my sessions"
-      - "decision patterns"
-      - "review my decision history"

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

@@ -1,57 +0,0 @@
-VALIDATION:
-  1:
-    id: V1
-    rule: evidence_grounded
-    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.
-    severity: critical
-    checks:
-      - "Each profile entry traces to a source record"
-      - "No profile entry is fabricated without evidence"
-  2:
-    id: V2
-    rule: confidence_calibration
-    description: >-
-      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.
-    severity: critical
-    checks:
-      - "Confidence values fall within protocol tier boundaries"
-      - "Single-source entries are capped at CS4 (30-49)"
-  3:
-    id: V3
-    rule: tension_honesty
-    description: >-
-      Contradictions MUST be recorded as tensions, not smoothed into a
-      coherent narrative. When evidence conflicts, the tension section
-      captures the divergence explicitly.
-    severity: critical
-    checks:
-      - "Conflicting evidence produces tension entries"
-      - "No smoothing over contradictions"
-  4:
-    id: V4
-    rule: read_only_sources
-    description: >-
-      Profilera MUST NOT modify session history, memory files, or config
-      files. It reads these sources for extraction but never writes to them.
-      The only artifact profilera produces is PROFILE.md.
-    severity: critical
-    checks:
-      - "No writes to session history files"
-      - "No writes to memory or config files"
-  5:
-    id: V5
-    rule: prediction_accuracy
-    description: >-
-      Full mode MUST validate predictions against 5 decision-rich prompts
-      not used to create the profile. Accuracy below 3/5 triggers a flag
-      noting categories needing more signal.
-    severity: warning
-    checks:
-      - "5 predictions tested against held-out prompts"
-      - "Accuracy below 3/5 is flagged in profile header"

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

@@ -1,80 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: vision
-    local_role: produces_and_consumes
-    description: >-
-      Realisera consumes this through CLI execution_context caveats or explicit
-      fallback state when available, and never modifies it during cycles. Created
-      during brainstorm (bootstrap or user-requested refinement).
-  2:
-    id: A2
-    artifact_id: todo
-    local_role: produces_and_consumes
-    description: >-
-      Realisera consumes TODO state from execution_context and included hej state
-      before direct reads, then writes newly discovered issues and resolved
-      entries. Severity classified per protocol SI1-SI4.
-  3:
-    id: A3
-    artifact_id: changelog
-    local_role: produces_and_consumes
-    description: >-
-      Realisera consumes changelog boundary from execution_context or the listed
-      CLI fallback before direct reads. It appends public change entries under
-      [Unreleased] based on commit type and promotes on version bumps.
-  4:
-    id: A4
-    artifact_id: progress
-    local_role: produces_and_consumes
-    description: >-
-      Operational cycle log. Realisera consumes latest progress evidence from
-      execution_context first, then appends one entry per cycle with mandatory
-      Verified field. Compacted by applying schema COMPACTION rules.
-  5:
-    id: A5
-    artifact_id: health
-    local_role: consumes
-    description: >-
-      Realisera consumes health state from execution_context and included hej
-      state before direct reads, focusing on critical and degraded findings for
-      work selection.
-  6:
-    id: A6
-    artifact_id: decisions
-    local_role: consumes
-    description: >-
-      Realisera consumes decision caveats and fallback commands from
-      execution_context first. Firm (DL1) entries are constraints and exploratory
-      (DL3) entries are uncertain foundations during work selection.
-  7:
-    id: A7
-    artifact_id: plan
-    local_role: produces_and_consumes
-    description: >-
-      Realisera consumes selected task, acceptance criteria, dependencies,
-      constraints, and source contract metadata from CLI execution_context before
-      direct plan reads, then updates task status and surprises during execution.
-  8:
-    id: A8
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Realisera consumes hej profile summary first. Missing or stale profile state
-      is a caveat and does not authorize profile refresh or direct profile reads
-      during normal startup.
-  9:
-    id: A9
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Realisera consumes artifact mappings and docs caveats from execution_context
-      and included hej docs state before direct docs reads.
-  10:
-    id: A10
-    artifact_id: design
-    local_role: consumes
-    description: >-
-      Realisera treats design state missing from execution_context as a caveat or
-      fallback-only need, and reads it only when building user-facing features
-      after listed CLI fallbacks are exhausted.

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

@@ -1,39 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests realisera for autonomous development.
-    priority: high
-    patterns:
-      - "realisera"
-      - "/realisera"
-  2:
-    id: T2
-    description: >-
-      Development cycle requests. Matches when the user wants to run an
-      autonomous development cycle or evolve the project.
-    priority: medium
-    patterns:
-      - "run a dev cycle"
-      - "evolve the project"
-      - "develop autonomously"
-      - "build the next feature"
-  3:
-    id: T3
-    description: >-
-      Continuous development signals. Matches when the user wants ongoing
-      building or to start working on the project.
-    priority: medium
-    patterns:
-      - "keep building"
-      - "start building"
-      - "work on the project"
-  4:
-    id: T4
-    description: >-
-      Vision refinement within a development context. Matches when the user
-      wants to refine the project vision as part of a development session.
-    priority: medium
-    patterns:
-      - "refine the vision"

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

@@ -1,110 +0,0 @@
-VALIDATION:
-  1:
-    id: V1
-    rule: verified_field_mandatory
-    description: >-
-      Every PROGRESS.md cycle entry MUST have a verified field. The field
-      carries either observed output from the primary entrypoint, an allowlisted
-      N/A tag, or a free-form rationale of at least 8 words.
-    severity: critical
-    checks:
-      - "Every cycle entry has a verified field"
-      - "verified field is not empty"
-  2:
-    id: V2
-    rule: one_cycle_per_invocation
-    description: >-
-      Realisera executes exactly one cycle per invocation. After logging (Step 9),
-      the capability MUST stop. Multiple cycles require separate invocations or
-      /loop.
-    severity: critical
-    checks:
-      - "Only one cycle entry appended to PROGRESS.md per invocation"
-  3:
-    id: V3
-    rule: no_remote_push
-    description: >-
-      Realisera MUST NEVER push to any remote repository. All commits are local
-      only. Remote operations require explicit user instruction outside this
-      capability.
-    severity: critical
-    checks:
-      - "No git push commands issued"
-  4:
-    id: V4
-    rule: vision_readonly_during_cycle
-    description: >-
-      The canonical vision artifact MUST NOT be modified during a cycle. It may only be written
-      during a brainstorm session (bootstrap or user-requested refinement).
-    severity: critical
-    checks:
-      - "Vision artifact not modified outside brainstorm"
-  5:
-    id: V5
-    rule: consecutive_failure_guard
-    description: >-
-      If the last 3 PROGRESS.md entries all record failed cycles, realisera
-      MUST stop and surface the pattern to the user. Do not attempt a 4th
-      consecutive cycle on the same failing problem.
-    severity: critical
-    checks:
-      - "Failure pattern checked before cycle start"
-  6:
-    id: V6
-    rule: artifact_path_resolution
-    description: >-
-      Before reading or writing any artifact, check .agentera/docs.yaml for path
-      overrides. If absent, use the default layout (TODO.md, CHANGELOG.md,
-      and DESIGN.md at root; canonical VISION.md at .agentera/vision.yaml;
-      other agent-facing artifacts as YAML in .agentera/).
-    severity: warning
-    checks:
-      - "DOCS.md checked before artifact access"
-  7:
-    id: V7
-    rule: execution_context_first
-    description: >-
-      Realisera startup SHOULD begin from `agentera prime --context realisera
-      --format json` and consume complete execution_context
-      state before direct reads of plan, progress, TODO, docs, health,
-      decisions, changelog, vision, profile, or design artifacts.
-    severity: warning
-    checks:
-      - "execution_context requested through supported prime --context seam"
-      - "complete execution_context used before direct startup artifact reads"
-  8:
-    id: V8
-    rule: fallback_before_raw
-    description: >-
-      When execution_context is incomplete or caveated, Realisera MUST run listed
-      CLI fallback commands before any last-resort raw artifact diagnostic and
-      MUST preserve caveats in cycle reporting.
-    severity: critical
-    checks:
-      - "CLI fallback commands run before raw artifact diagnostics"
-      - "execution_context caveats preserved in progress or cycle report"
-  9:
-    id: V9
-    rule: context_generation_readonly
-    description: >-
-      Generating execution_context is read-only. It MUST NOT refresh profile or
-      installed app state, edit vision or objective state, spawn workers, commit,
-      push, tag, publish, or introduce unsupported capability-name CLI commands.
-    severity: critical
-    checks:
-      - "No protected state mutation during context generation"
-      - "No unsupported `agentera realisera` or `agentera build` command introduced"
-  10:
-    id: V10
-    rule: satisfaction_authority_boundary
-    description: >-
-      When Realisera touches decision satisfaction, it may mark 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
-      or claim it proved user intent.
-    severity: critical
-    checks:
-      - "Provisional satisfaction requires evidence"
-      - "Only the user confirms final satisfaction"
-      - "Missing or compacted satisfaction caveats are preserved"

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

@@ -1,47 +0,0 @@
-ARTIFACTS:
-  1:
-    id: A1
-    artifact_id: decisions
-    local_role: produces_and_consumes
-    description: >-
-      Reasoning trail with confidence labels. Resonera reads existing decisions
-      through `agentera decisions --format json` and its source_contract to avoid
-      re-deliberation, and writes new decision entries with confidence (DL1
-      firm, DL2 provisional, DL3 exploratory). Compact older entries by applying
-      schema COMPACTION rules; incomplete compacted entries are caveated context,
-      not a reason for historical reconstruction during normal deliberation.
-  2:
-    id: A2
-    artifact_id: vision
-    local_role: produces_and_consumes
-    description: >-
-      Resonera may update project direction only with explicit user
-      confirmation when a decision feeds into project direction. Read for
-      context during deliberation.
-  3:
-    id: A3
-    artifact_id: todo
-    local_role: produces_and_consumes
-    description: >-
-      Resonera may add tech debt items surfaced during deliberation only with
-      explicit user confirmation. Severity per protocol SI1-SI4.
-  4:
-    id: A4
-    artifact_id: objective
-    local_role: produces_and_consumes
-    description: >-
-      Resonera may write optimization decisions only with explicit user
-      confirmation when a decision feeds into what to optimize.
-  5:
-    id: A5
-    artifact_id: profile
-    local_role: consumes
-    description: >-
-      Resonera reads this at session start to acknowledge high-confidence
-      entries and avoid re-deliberating settled ground.
-  6:
-    id: A6
-    artifact_id: docs
-    local_role: consumes
-    description: >-
-      Resonera reads this first to resolve project-local artifact mappings.

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

@@ -1,46 +0,0 @@
-TRIGGERS:
-  1:
-    id: T1
-    description: >-
-      Direct invocation by name or slash command. Matches when the user
-      explicitly requests resonera for structured deliberation.
-    priority: high
-    patterns:
-      - "resonera"
-      - "/resonera"
-  2:
-    id: T2
-    description: >-
-      Decision-oriented requests. Matches when the user wants help thinking
-      through a decision or evaluating tradeoffs.
-    priority: medium
-    patterns:
-      - "deliberate"
-      - "help me think through"
-      - "help me decide"
-      - "think this through with me"
-      - "let's deliberate"
-      - "what are the tradeoffs"
-      - "brainstorm"
-      - "rubber duck"
-  3:
-    id: T3
-    description: >-
-      Option-comparison signals. Matches when the user is torn between
-      choices or wants to evaluate competing approaches.
-    priority: medium
-    patterns:
-      - "should I"
-      - "I'm torn between"
-      - "what's the right approach"
-      - "let's reason about"
-  4:
-    id: T4
-    description: >-
-      Pre-build scoping signals. Matches when the user wants to scope or
-      reason about work before starting implementation.
-    priority: medium
-    patterns:
-      - "scope this out"
-      - "before I build this"
-      - "talk me through"

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

@@ -1,77 +0,0 @@
-VALIDATION:
-  1:
-    id: V1
-    rule: one_question_per_turn
-    description: >-
-      Resonera MUST ask exactly one question per turn. Compound questions
-      are not allowed. Every question MUST include a Done option.
-    severity: critical
-    checks:
-      - "At most one question per response"
-      - "Done option present"
-  2:
-    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.
-    severity: critical
-    checks:
-      - "User confirmation obtained before writing to VISION.md, OBJECTIVE.md, or TODO.md"
-  3:
-    id: V3
-    rule: decision_confidence_required
-    description: >-
-      Every DECISIONS.md entry MUST have a Confidence field with one of the
-      protocol-defined labels: firm (DL1), provisional (DL2), or
-      exploratory (DL3).
-    severity: critical
-    checks:
-      - "Decision entry has Confidence field"
-      - "Confidence value is one of firm, provisional, exploratory"
-  4:
-    id: V4
-    rule: preserved_decision_fields
-    description: >-
-      DECISIONS.md entries MUST preserve the canonical top-level fields:
-      Question, Context, Alternatives, Choice, Reasoning, Confidence,
-      Feeds into. Win conditions stay inside Alternatives bullets.
-    severity: critical
-    checks:
-      - "Decision entry has all canonical fields"
-  5:
-    id: V5
-    rule: no_implementation
-    description: >-
-      Resonera MUST NOT skip to implementation. It deliberates; other
-      capabilities build. If the user wants to build, route to the
-      appropriate capability.
-    severity: critical
-    checks:
-      - "No code changes made during deliberation"
-  6:
-    id: V6
-    rule: red_flag_phrasing_banned
-    description: >-
-      Red-flag phrasing that weakens the challenge is banned: "That sounds
-      reasonable", "Either way is fine", "It depends" without naming the
-      variable, "There is no wrong answer here", "Both options are valid"
-      when one conflicts with constraints.
-    severity: warning
-    checks:
-      - "No red-flag phrases in output"
-  7:
-    id: V7
-    rule: satisfaction_authority_boundary
-    description: >-
-      When Resonera 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;
-      automation must not reconstruct hidden outcomes or claim it proved user
-      intent.
-    severity: critical
-    checks:
-      - "Provisional satisfaction requires evidence"
-      - "Only the user confirms final satisfaction"
-      - "Missing or compacted satisfaction caveats are preserved"