Schema refactor
Implements PaymentRequest v3.
CURRENT CONTRACT$299 · PerpetualGet Coding AcceleratorGet — $299
About Coding AcceleratorThe project itself
The project itself
should remember.
AI coding assistants can reason brilliantly inside a session. The project cannot depend on that session remaining open, uncompacted, and perfectly remembered.
Architecture, constraints, debugging history, rejected approaches, current work, and next actions need a durable place outside any one assistant's temporary context.
01 · ONEProject truth outlives the session.02 · MANYAgents work from one project mind.03 · SYSTEMEvidence extends beyond the codebase.
Many agents. One project mind.
THE FOUNDING PROBLEMSoftware projects do not forget.
Software projects do not forget.
Sessions do.
A developer teaches an assistant how the system actually works: where identity belongs, which constraints cannot move, what failed in production, why a tempting design was rejected, and what must happen next.
That working context becomes genuinely valuable. Then compaction summarizes it, a terminal closes, an agent restarts, or tomorrow begins in a new session.
The repository still contains the code. It does not necessarily contain the reasoning that made the code correct. The developer must reconstruct the same project reality before meaningful work can continue.
Compaction forgets. Coding Accelerator remembers.WORKING CONTEXTGateway owns external identity validation.
Reason · Internal services must not validate external identity tokens directly.
Rejected · Per-service authentication!
SESSION COMPACTEDTemporary context summarized
PROJECT INTELLIGENCEDecision available to the next sessionEvidence · status · reasoning · affected work
WHY MANY CHANGES THE PROBLEMOne temporary memory becomes
One temporary memory becomes
several competing realities.
Adding more agents does not merely multiply the first problem. It creates a second one.
Claude Code, Codex, Copilot, and other assistants can each hold a different version of the project. Their individual changes may be reasonable while the combined result still conflicts.
API handler
Updates the gateway for v3.
CURRENT CONTRACTCheckout interface
Still builds against PaymentRequest v2.
STALE ASSUMPTIONSwitchboard coordinates the MANY.
Agents, sessions, tasks, branches, changed files, shared decisions, possible overlap, and handoff state become one inspectable project operation.
WHY PROJECT TRUTH MATTERSProject Truth is not
Project Truth is not
a longer prompt.
A long prompt can contain more text and still fail to identify what the project currently believes. Project Truth makes status explicit and keeps the reasoning and evidence attached.
It allows retrieval and hydration to answer a harder question than “what was mentioned?”
What is true for this task, right now—and why?
CURRENT
●What the project presently accepts
REJECTED
—What was considered and ruled out
SUPERSEDED
—What a later decision replaced
CONFLICTING
!What still requires resolution
THE NEXT LAYER · SYSTEMThe project is larger
The project is larger
than the codebase.
A modern feature can cross source code, routes, APIs, schemas, services, queues, events, WebSockets, webhooks, infrastructure, cloud resources, authentication rules, SaaS, B2B integrations, deployment, and external partners.
No individual coding session sees that entire execution path. The connections—and the technical agreements those connections depend on—need continuity too.
ACTUAL PROJECTSource · APIs · Services · SchemasCLOUDIDENTITYQUEUESSAASB2BPARTNERS
PROTOCOL LOOM · POST-MVP / EXPLORATORYThe architecture beyond
The architecture beyond
agent coordination.
Protocol Loom is the broader SYSTEM-level direction: a non-owning observation, topology, tracing, contract, verification, and continuity layer surrounding the actual technical project.
Protocol Loom
The non-owning observation, topology, tracing, contract, verification, and continuity wrapper around the actual technical project and system surface.
Protocol Weave
The complete known, evidence-backed topology of the system or application surface being observed.
Feature
A logical product or system capability containing one or more end-to-end Protocol Threads.
Protocol Thread
One end-to-end functional execution or connectivity path through the system.
Protocol Splice
One specific connection or join between two components within a Protocol Thread.
Protocol Contract
The technical rules that both sides of a Protocol Splice must agree on.
Protocol Loom observes permitted evidence without owning application business logic or execution.
It must not hallucinate topology or present unsupported relationships as verified.
Only safe references, expectations, metadata, and contract information are mapped.
WHY NATIVE WINDOWSA developer instrument.
A developer instrument.
Not another chat interface.
Coding Accelerator belongs beside the repository, terminals, worktrees, editors, and local tools where project decisions are made.
A native Windows control plane can make project state, storage boundaries, active workstreams, hydration context, and evidence visible without pretending to be the coding assistant itself.
The assistant works on the task. Coding Accelerator helps the project remember the work.CODING ACCELERATOR— □ ×
PROJECT COMMAND CENTER
Project Truth
Capture freshness CurrentHydration readiness ReadyUnresolved conflicts 2Storage visibility VisiblePRODUCT PRINCIPLESControl before convenience.
Control before convenience.
Evidence before inference.
Truthfulness
Represent what the project knows, what it no longer believes, and what remains unresolved—without quietly collapsing those states together.
Evidence
Important project intelligence should retain its source, reasoning, status, and affected work instead of becoming an unsupported summary.
Local-first operation
The native desktop experience keeps project intelligence close to the development workflow and visible under developer control.
Interoperability
The project mind should outlive any one model, provider, terminal, editor, or coding-agent interface.
Safe secret handling
Map references, expectations, and metadata where needed—never actual secret, key, private-key, credential, or bearer-token values.
No fabricated project state
Missing evidence must remain missing. Candidate relationships must not be presented as verified facts.
THE HUMAN REASONBuilt for the person who keeps
Built for the person who keeps
having to explain it again.
The origin does not require an invented founder mythology. It begins with a familiar developer experience: teaching a capable machine the same project truth for the fourth time.
Coding Accelerator is being built for developers who care about why the system is in its current state—not only what files happen to exist now.
It is for teams that want AI-assisted development to remain inspectable, continuous, and under project control as the number of sessions, agents, and technical connections grows.
Unify Agents. Accelerate Code Development.Give the project durable
intelligence of its own.
Stop rebuilding the same context and coordinating agents by hand. Keep the decisions, evidence, constraints, and current work available beyond any one session.
Many agents. One project mind.Windows desktop · One-time purchase · Perpetual license