
pantheon
two gods. one brain.
a working harness for code, content, and judgment.
the twins

janus
v0.1.0Project harness for tiered, verified, scope-controlled work across code, content, and judge tasks.
/plugin install janus
argus
v0.1.0Lean Codex workflows for scoped work, validation, release, and learning.
/plugin install argusthe stoa (skill catalog)
janus-build-mode
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.
janusjanus-content-mode
Use for copy, scripts, social posts, emails, YouTube descriptions, event packets, sponsor outreach, marketing campaigns, and any output that is finished, copy-paste-ready text rather than code.
janusjanus-judge-mode
Use for Warhammer 40K rules questions, event judging, ruling on a specific interaction, resolving timing windows, or producing a tournament ruling with source citation.
janusjanus-plugin-build
Use when building a new Claude Code plugin from scratch, scaffolding a plugin structure, or porting an existing skill into a plugin. Covers manifest, hooks, sub-skills, validator, tests, and the retrospective loop.
janusjanus-router
Use when starting any project work in a janus-managed folder, when a .janus/ directory is present, or when the user says /start, /continue, /audit, /deploy, /checkpoint, /generate, /recover, or references tiers, harness, or scoped project work. Routes to the narrowest janus sub-skill.
janusjanus-tier1-quick
Use for a single quick task — short rewrite, one-line answer, small social post, simple naming or formatting, one-off question — when no project state needs to be loaded.
janusjanus-tier2-project
Use for normal project work — repo task, bug fix, feature add, video folder, event packet, design iteration, marketing campaign, copy edit, landing page update, or resuming previous project work. The default tier when unclear.
janusjanus-tier3-system
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.
janusjanus-worklog
Use at the end of any meaningful work session to update the project's continuity log — what changed, what was learned, what is next. Also use when resuming work and the prior WORKLOG must be read.
janusonslaught-engineering
Use for Onslaught Gaming code projects — starting, resuming, auditing, or deploying. Covers the 7 gates, the 14 commands, the deploy matrix, the audit checklist, and the security discipline that Onslaught code must meet before reaching production.
januspantheon-site-build
Use when building a Next.js + Cloudflare Pages catalog site that reads sibling plugin manifests at build time. Covers content sources, PII tripwire, design system tokens, and the apotheosis page pattern.
janusargus-handoff-builder
Use to create precise Codex handoff prompts with exact repo path, objective, allowed and forbidden changes, files to inspect or change, validation commands, required output, stop conditions, and confidence threshold.
argusargus-project-gate
Use as the first Argus gate when starting work in a Codex project or repo; inspect the project, recommend the workflow and skills, ask for confirmation, detect missing skills, and set validation gates before implementation.
argusargus-project-inventory
Use to safely inventory a parent folder of Codex projects, classify projects without reading secrets, identify frameworks and validation commands, recommend Argus workflows, and extract reusable skill opportunities.
argusargus-release-packaging
Use for Argus-style release packaging, versioned ZIP generation, pre-package validation, artifact exclusion rules, release report creation, and package integrity checks.
argusargus-repo-intake
Use for Argus-style repository intake, baseline mapping, architecture discovery, required-file inspection, risk identification, and preparing a scoped work plan before edits.
argusargus-retrospective-capture
Use to capture reusable lessons from Codex work, identify repeated friction, propose skill or reference improvements, and prevent uncontrolled memory or context bloat.
argusargus-router
Use when the user asks to use Argus, Argus Command Center, command-center workflow, or wants help deciding which Argus workflow should handle a Codex task without loading unnecessary context.
argusargus-validation-gate
Use for Argus-style validation gates, repair-and-revalidate loops, markdown integrity checks, skill frontmatter checks, package metadata checks, and final validation reports.
argusinvocations (sample prompts)
“use janus build mode to scaffold a Cloudflare Worker”
routed plan, wrangler.toml, src/index.ts, and a deploy command to dry-run.
“use argus to validate a Codex handoff”
validation gate report: scope check, repo intake, and a pass/fail with concrete repairs.
“use janus judge mode for a 40K Strands-of-Fate timing question”
ruling with cited source page, timing-window resolution, and a single-line tournament line.
the oracle
Agents can programmatically provision Cloudflare infrastructure and get API tokens without human intervention — critical for autonomous deployment workflows.
Dynamic Workflows enable tenant-specific durable execution routing at scale, directly applicable to multi-tenant agent harness architectures on Workers.
- Running Codex safely at OpenAIOpenAI dev blog
Details OpenAI's production sandboxing and telemetry approach for Codex agents — directly transferable patterns for secure plugin execution environments.
- Advancing voice intelligence with new models in the APIOpenAI dev blog
New realtime voice models in the API expand plugin interaction modalities beyond text for more natural agent interfaces.
recorded 2026-05-12 · 4 entries
the vault (shared brain)
the brain
preview brain.json (operator fields elided)
{
"schemaVersion": 1,
"generatedAt": "2026-05-12T05:28:04.763Z",
"operator": {
"displayName": "—",
"handle": "—",
"org": "onslaught-gaming"
},
"projects": [
{
"slug": "pantheon",
"name": "pantheon",
"status": "active"
},
{
"slug": "janus",
"name": "janus",
"status": "active"
},
{
"slug": "argus",
"name": "argus",
"status": "active"
}
],
"taxonomy": {
"tiers": [
{
"id": 1,
"name": "quick",
"description": "single small task, no project state loaded"
},
{
"id": 2,
"name": "project",
"description": "scoped repo or content task with worklog"
},
{
"id": 3,
"name": "system",
"description": "production system spanning many folders and gates"
}
],
"modes": [
{
"id": "build",
"name": "build mode",
"description": "implementation-heavy code work"
},
{
"id": "content",
"name": "content mode",
"description": "copy and finished text"
},
{
"id": "judge",
"name": "judge mode",
"description": "rules and tournament rulings"
}
]
}
}the index
v0 · 0 entriesthe vault is empty.
offerings
auguries (changelog)
- I (1)2026-05
pantheon v0.1.0 — shipped
the catalog opens. static site reading janus and argus from disk at build time, with the eight inscriptions in place and a privacy tripwire at the gate.
- II (2)2026-04
janus v0.1.0 — shipped
tiered project harness for claude code. router, build / content / judge modes, validator, and the gate hook that keeps scope honest.


















