Hybrid runtime

pstack lives inside the worker.
Firstmate still runs the fleet.

Lauren Tan’s pstack (@poteto) is elite engineering discipline. Kun’s Firstmate (@kunchenguid) is fleet orchestration. I did not let their routers compete. I nested one inside the other.

Do not do this / do this

Two authorities

Routers fight

Two bosses pick work, isolate copies, and decide when to ship. Scale and discipline cancel each other out.

Firstmate router × pstack router

One runtime

Discipline nested in the worker

Firstmate still dispatches. pstack habits fire only on the worker that is writing code.

Firstmate fleet

pstack inner loop

just-in-time plays, real-artifact proof

Command hierarchy

Youmerge, product, credentials

Firstmatedispatch · isolate · supervise · deliver

Shipchange the product

Inner loopsmallest change · prove it

Scoutknowledge only

Name the gapwhat was not verified

Supervisorfleet, not code face

No pstack dumpstays out of always-on rules

Worker pipeline

1Load the playConditional brief. Only the habits this job needs.

2Subtract firstSmallest logical change. Blast radius named before extra code.

3Walk if neededOnly map how the system is built when the change crosses into another part of it. If you skip that, write one line saying why.

4Change in isolationOwn copy. Ship cannot become the fleet operator.

5Prove the artifactLive command, flow, record, or local verifier. Tests-exist is not done.

When how/why runs

Run the walk

Unfamiliar area, shared boundary, or diagnosis.

Then how (and why if history matters). teach is optional and does not edit code.

Do not run it

Ordinary local edit in a known file.

Skip with a one-line reason. Do not turn every ship into a research program.

Stripped on purpose

No Cursor UI

Habits rewritten onto the CLI stack already running the fleet.

No second router

pstack playbooks do not pick work. Firstmate already does.

No extra review tax