The approach
Constitution first. Agents second. Hooks enforce the rest.
A single rule file — twenty-five rules — loads at every session start. No agent can override it. Each agent is scoped to one concern and loads only the playbook and source files it needs. Hooks run between sessions to stamp state, trace sources, and surface drift.
The model runs locally via Claude Code on a Max plan. MCP extends the tool surface — file reads, script calls, renders, all within one session. No API tokens, no external calls, no data leaving the machine.
Facts only. No invention. Ever.
Every claim must trace to a source on disk. If a claim has no source, it does not appear. No exceptions. Ungrounded lines get flagged — the engine ships, but the flag becomes a ticket to resolve before the next run.
Rule 1 — loaded every session
Rule constitution
Twenty-five rules load at every session start. No agent can override them. Behavioral rules are always on; domain rules activate per agent.
Hook enforcement
Hooks run between sessions — stamping state on commit, scanning for drift on write, promoting stale questions into the ticket tree.
Scoped agents
Each agent loads one playbook and reads only the source files it needs. No agent sees the full system — only its concern.
Agentic architecture
Specialised agents, shared rules.
Each agent is scoped to one concern. It loads its own playbook, reads only the source files it needs, and hands off to the next agent via structured output. The rules constitution loads at every session start — no agent can override it. Hooks enforce by side-effect between sessions.
The pipeline
JD in, eight PDFs out.
A job description enters the system. The engine triages, tailors, validates, and renders. Every PDF is ATS-friendly — real embedded text, no flattened images, machine-readable section headers. The model only fills values the schema allows, with content the source corpus already contains.
Triages
7 decisions logged
| Employer | Role | Date | Verdict |
|---|---|---|---|
| Centro CX | Product Owner Digital CX (m/w/d) | 2026-05-23 | FIT |
| Alpine Fintech | Business Analyst Claims | 2026-05-23 | FIT |
| Solaris AG | Senior Product Manager (100%) | 2026-05-22 | SKIP |
| Neura Consulting | AI Domain Lead | 2026-05-22 | STRETCH |
| Pragma Engineering | Business Solution Architect – AI & UX | 2026-05-21 | STRETCH |
Every JD gets scored — FIT, STRETCH, or SKIP — before anything else runs. Only FIT and STRETCH proceed to tailoring.
summit re
Senior Product Owner
The interface — Variant
Language toggle. Status tracking. PDF on the fly.
Each variant shows the tailored content with a DE/EN toggle. Status moves from draft through applied. The PDF renders on download — page-count cap and ATS extraction enforced at render time. If either check fails, the build fails.