What is Reticle Systems?
Reticle Systems is becoming a deterministic software project definition and planning system. It turns an incomplete idea into a canonical, testable ProjectSpec and then compiles that specification into build-ready artifacts.
Product / deterministic software project planning
Reticle Systems
Define the software project before an agent starts building.
Last reviewed 2 September 2026
Active development — deterministic planning core implemented
Website: reticlesystems.co.uk — coming soon. The current public product source is the GitHub repository.
What changed in the positioning?
Earlier public material led with BuildProof, scanner and launch-readiness language. The current Phoenix direction leads with planning before building: idea → deterministic questions and evidence → canonical ProjectSpec → readiness and conflict checks → compiled outputs.
What is implemented?
- Versioned ProjectSpec with stable/content-derived identity and deterministic serialization.
- Declarative question engine with profiles, applicability, dependencies and deterministic sequencing.
- Technology catalogue and explainable recommendation rules with accept, reject and alternative decisions.
- Readiness linter, contradiction detection and deterministic compilation.
- ProjectSpec JSON, Project Bible, build plan, agent instructions, requirements, technology decisions and unresolved-items/evidence register outputs.
Why define before building?
AI-assisted builds can move quickly while requirements and architecture remain ambiguous. Reticle is intended to make the decisions and unknowns explicit first, so the resulting outputs can be handed to coding agents rather than asking a model to invent the project plan from scratch.
Current implementation boundary
The verified Phoenix core is deterministic and LLM-free for its /define flow. MCP/WebMCP, cloud persistence, richer extraction and further integrations are later work and are not claimed as shipped on this page.
Future roadmap
From canonical definition to a wider planning system.
- Continue sealing the deterministic core and its preservation/traceability contract.
- Expose the planning core as a headless service.
- Add MCP integration for submitting an idea and receiving canonical planning artifacts with their ruleset and evidence context.
- Extend structured extraction and project-document support where justified by evidence.
- Add richer human/manual editing surfaces later.
These are roadmap directions, not claims of current availability.
Source and evidence
Inspect the Phoenix planning core.
- View public source repositoryCanonical public repository
- Inspect the ProjectSpec evidencePublic Phoenix branch commit
- Read the question engine notesDeclarative, profile-aware sequencing
- Read the technology rulesDeterministic recommendations and explicit decisions
Portfolio relationship
A potential downstream presentation path.
PlainSpeak
Potential deterministic presentation layer for human-readable planning outputs; a shipped integration is not claimed.
FAQ
Is Reticle Systems primarily a scanner?
The older public positioning led with scanning and launch-readiness. The current Phoenix direction is a deterministic planning core for defining a project before building; inspection and audit remain possible later parts of the wider journey.
Is reticlesystems.co.uk live?
No. The planned domain is shown as “reticlesystems.co.uk — coming soon” and is not presented as an active product surface here.