VIII (8)

janus-tier3-system

janus

Use for production system work — full agentic system, MCP-connected workflow, judge engine, automation pipeline, security audit, multi-step deploy, or any task spanning many folders and verification gates.

Janus Tier 3 — System / Production Work

IWhen To Use

  • Full agentic system or MCP-connected workflow.
  • Automated pipeline, judge engine, or recurring production process.
  • Security audit on a production code project.
  • Multi-step deploy from scratch.
  • Work that earns the weight of the full harness.

Tier 3 is not better than Tier 2. It is heavier. Use it only when the task earns it.

IIWhat To Load

Required:

  1. .janus/PROJECT_CONTEXT.md and .janus/WORKLOG.md for the project.
  2. references/HARNESS_SPEC.md
  3. references/PROGRESSIVE_DISCOVERY.md
  4. references/PROGRAMMATIC_TOOL_CALLING.md
  5. references/TIER_MATRIX.md

By discovery:

  • $onslaught-engineering for Onslaught code (7 gates, deploy matrix, audit checklist).
  • The relevant mode skill (Build, Judge, or Content).
  • A specific template from templates/.

IIIWorkflow

  1. Read required files.
  2. Identify the gates this work must close (mission, contracts, knowledge, reliability, security, observability, product).
  3. For repeated tool operations, prefer a script over a chain of small calls (see references/PROGRAMMATIC_TOOL_CALLING.md).
  4. Verify at every gate. Do not skip Gate 5 (security).
  5. Run the project's validator before reporting completion.
  6. Update .janus/WORKLOG.md via $janus-worklog.

IVOutput

Completed.

Changed:
- path

Verified:
- command : result

Notes:
- one concise note

Next:
- one action

VHard Laws

  • Verify before modifying.
  • Do not mix package versions.
  • Two strikes then ask.
  • Never claim completion without a Verified: line.
← back to the stoa