ForgeSDLC
Navigate
Home
Discover ForgeSDLC (101)
Practice (201)
Master (301)
Blog

Versona-owned execution tasklets (Docker / browser / API)

Cognition tasklets (Cursor rules) live under Forge tasklets/. Execution tasklets are recipes or wrappers that run outside the IDE LLM and return artifacts (files, logs, exit codes) for a Versona or human to review.

Pattern

  1. Versona or meta-agent defines inputs, success criteria, and expected artifacts (e.g. export.pdf, screenshots/, run.log).
  2. Recipe under agents/recipes/<name>/ implements the run (see ORCHESTRATION.md).
  3. Cursor / CI invokes the recipe; the LLM does not replace the container — it interprets outputs.

Execution tasklet swimlanes

Cognition defines criteria and artifacts; recipes run outside the IDE and return reviewable outputs.

  1. PatternThe split between cognition tasklets and execution recipes on this page.
  2. Lane AThe execution plane where bounded recipes produce concrete artifacts.
  3. handoffCursor or CI invokes the recipe with project-specific inputs.
  4. shared outcomeExpected artifacts land as files, logs, or exit codes for review.
  5. Lane BThe review plane where Versona or human interprets run outputs.
  6. inspect / adaptReviewers read artifacts against the defined success criteria.
  7. feedbackFindings fold back into inputs, criteria, or the next recipe invocation.

Example manifest (conceptual)

Project-specific JSON or env file passed to the recipe (not frozen in blueprints):

{
  "recipe": "notebooklm-export",
  "inputs": { "source_dir": "docs/product/vision", "template": "exec-brief" },
  "outputs_expected": ["artifacts/deck-spec.json", "artifacts/run.log"],
  "secrets": "env:NOTEBOOKLM_SESSION"
}

After the run, register concrete paths in a session artifact-manifest.json when the team adopts optional schemas — see ../../sdlc/methodologies/forge/schemas/artifact-manifest.schema.json and ../../sdlc/methodologies/forge/VERSONA-OPERATING-MODEL.md §2.

Security

  • No secrets in blueprint Markdown. Use CI secrets and gitignored .env patterns per POLICY.md.
  • Network and browser recipes are high risk — restrict images, cap runtime, log URLs.
  • STRUCTURE.md — L5 recipes, L6 optional runner
  • sdlc/methodologies/forge/tasklets/TASKLET-TAXONOMY.md — execution plane row
  • sdlc/methodologies/forge/versona/VERSONA-SKILL-MATRIX.md — which Versona uses which Skill vs recipe
  • Blueprint stub templates (copy to agents/recipes/): ../templates/recipe/versona-evidence-pack-assemble/, ../templates/recipe/versona-kitchensink-diagram-export/