Telstar is an evolving open architecture for turning organizational knowledge into evidence that machines can reason over deliberately. This page is the technical view — the decision tiers, the knowledge model, and an honest account of what exists today.
The architecture is being developed around escalation: resolve a question at the lowest tier that is genuinely sufficient, and escalate deliberately when the evidence does not support an answer. Cost matters, but so does declining to answer.
Permissions, policy, lifecycle and conflict edges. Settles what a lookup or a hard rule can settle.
Routing, relevance ranking, and a judgement about whether the retrieved evidence is actually enough.
Specialized mechanisms for bounded decision classes with a closed set of outcomes.
Intended for genuinely residual ambiguity, reached with better structured context when it is needed.
Implemented = present in the current codebase. In development = actively being built. Planned = designed direction, not yet built.
Conceptual architecture, not a deployed system. The tiers above describe how the decision path is designed to work.
Telstar is designed around structured records rather than loose passages. A record is modelled to carry its authority, its conditions, whether it is current, and what it replaces — so that a decision can lean on it deliberately rather than hopefully.
A claim about how the company works
A node moves through guarded states rather than being trusted on arrival. Transitions are enforced, not advisory.
Sources are ordered by the class of authority they carry, not by the form they arrive in. An official document and an official page belong to the same class; a help-centre article and a sales note do not.
Implemented the node model, lifecycle, and authority classes
Observatory is the intended surface for inspecting and governing the system — where knowledge, evidence, and decisions move, and what the system has declined to answer.
A planned control plane for understanding how knowledge, evidence, and decisions move through Telstar.
We have not designed or prototyped a production interface for Observatory. It is represented here architecturally, because showing a finished-looking console would describe work that does not exist.
The same applies to the rest of the product surface. Polaris is implemented as a knowledge core and store; Orbits exist as a permission and scope model. Neither has a finished interface.
Telstar is early-stage and under active development. This page distinguishes what exists from where the architecture is headed, because the difference matters when deciding whether to work with us.
A knowledge system that can reason about authority, sufficiency, conflict, and escalation — before asking a frontier model to decide.