Simon
simon.nofinway.comThe public-facing gateway surface. This is the entry point that carries routing, SSL termination, and the outward-facing application presence.
gateway
public entry point
routing and SSL
Two public surfaces are in view right now: Simon as the main gateway presence, and Oxen as a separate hosted application surface. Behind them sits the same broader operating model: the developer and local AI build inside the repo, while Pubert operates around that repo as a DevOps team member for continuity, deployment, and diagnosis.
Pubert is the management layer around the repo and infrastructure. Its function is to preserve context, coordinate the environment, and keep the decision trail intact so the app can be deployed and diagnosed reliably.
Simon is the gateway and public face. Simon2 is the subconscious engine room carrying the heavier storage, memory, and processing responsibilities.
The ratcheting protocol controls execution: lock the plan through ADRs and manager notes, delegate narrow changes, and keep progress forward-only and auditable.
The application itself is built inside the repo by you and your local AI. Pubert is a separate concern around that work, closer to a DevOps team member than an app-coding peer.
The public-facing gateway surface. This is the entry point that carries routing, SSL termination, and the outward-facing application presence.
A separate served application surface under the same broader ecosystem, presented as its own domain while still benefiting from the prepared infrastructure around it.
From the DevOps agent point of view, this is a segmented development ecosystem: the repo is where the application is built, and the surrounding layer is where deployment, diagnosis, and continuity are managed.
Pubert carries forward state: who matters, what changed, what remains open, and which environment assumptions are already locked in around the repo.
The critical move is to convert decisions into a forward-only execution path, then bring in specialized agents for surgical changes rather than open-ended improvisation.
You remain the architect and auditor, and your local AI helps build the application in the repo. Pubert handles the deploy-and-diagnose layer and leaves the transparency trail in the logs.