I (1)

janus-build-mode

janus

Use for implementation-heavy code work — patching a repo, adding a feature, fixing a bug, running tests/builds, preparing a deploy. The default mode for any project that is a code repo.

Janus Build Mode

IWhen To Use

  • Any task that edits source code in a repo.
  • Bug fixes, feature work, refactors, deploys.

IIWorkflow

  1. Inspect before touching. Read the affected files.
  2. Run git status before any commit suggestion.
  3. Patch only what is needed. Preserve public contracts.
  4. Run available tests, builds, lints, type checks.
  5. Bump version or cache-bust only when project policy requires it.
  6. Update .janus/WORKLOG.md at end of meaningful work.
  7. If the repo is an Onslaught project, load $onslaught-engineering for gates and deploy matrix.

IIIVerification Before Completion

Before claiming completion, run at least one of:

  • The project's test suite.
  • The project's build.
  • A targeted script that proves the change works.

Report the exact command and its result on a Verified: line.

IVProgrammatic Execution

For repeated operations across many files (secret scan, syntax check, bulk format), prefer a single script over a chain of small tool calls. See references/PROGRAMMATIC_TOOL_CALLING.md (Tier 3) for the pattern.

VFailure Escalation

  • First fail: try once more with a different approach.
  • Second fail: stop. Report exactly what failed and why. Propose the correct next step. If unsure, ask.

VIHard Laws

  • Do not mix old and new package versions.
  • Do not leave partial implementations.
  • Do not commit secrets. Use platform secrets (Wrangler secrets, env vars, dashboards).
  • Do not skip security review for production code.
← back to the stoa