The Locked-Down Deploy

Step 1 · Frame the problem · OBSERVATION

The engineer frames the environment. Claude takes in the constraints. Neonmem stores the first picture of the network.

Step 2 · Frame the problem · OBSERVATION

The engineer adds the awkward details. Claude notes them. Neonmem keeps each constraint beside the project.

Step 3 · Frame the problem · QUESTION

The engineer raises an open question. Claude holds it open. Neonmem records the question for the debate.

Step 4 · Design debate · HYPOTHESIS

The engineer floats an approach. Claude treats it as a hunch to test. Neonmem files it as a hypothesis.

Step 5 · Design debate · DEBATE

The engineer opens a debate. Claude lays out both options. Neonmem starts a debate thread.

Step 6 · Design debate · ARGUMENT

The engineer weighs speed against compliance. Claude balances them. Neonmem links each argument to the debate.

Step 7 · Design debate · RESOLUTION

The engineer decides. Claude commits to the compliant path. Neonmem stores the resolution permanently.

Step 8 · Make it work · ACTION

The engineer asks for the change. Claude configures the route. Neonmem logs the action.

Step 9 · Make it work · CONCLUSION

The engineer confirms success. Claude validates the route. Neonmem records it as the working path.

Step 10 · Hit a wall · DEAD_END

The engineer flags a silent failure. Claude marks it. Neonmem stores a permanent dead-end so no one re-trips the firewall.

Step 11 · Hit a wall · RULE

The engineer sets a rule. Claude adopts it. Neonmem pins it near the core.

Step 12 · Instant knowing · PROCEDURE

The engineer records the safe procedure. Claude captures the steps. Neonmem stores the how-to.

Step 13 · Instant knowing · REFLEX

The engineer sets the guiding principle. Claude internalizes it. Neonmem keeps it as a reflex.

Step 14 · Lean on memory · RECALL

The engineer asks for the route. Claude answers from memory. Neonmem surfaces the working path and the procedure.

Step 15 · Lean on memory · DEAD_END_CHECK

The engineer almost reopens a bad idea. Claude warns it's a recorded dead-end. Neonmem flags the failure and why.

Step 16 · Lean on memory · TIMELINE

The engineer asks what happened today. Claude replays it in order. Neonmem returns it by time, not a guess.

Step 17 · Let it sleep · DREAM

The engineer wraps up. Claude consolidates. Neonmem merges the chatter and keeps the constraints, dead-ends and rules.