The architecture
Every product, framework, and seam, with paths and contract authorities.
Core/ECOSYSTEM-ARCHITECTURE-2026-05-20.mdParallax is a viewpoint name for the overhead view of a coherence stack: a spine of composable products and frameworks, organized on two structural axes and one production chain, composing along one loop (Notice, Spec, Execute, Observe), governed by the Intent operating model. It is not a product, not a container, and not a methodology book. It is the surface from which the relationships between the parts become legible — and challengeable.
Two vantage points, one distant object: depth appears when separated viewpoints are held together. That is what this system does to its own work.
Everything downstream of the model is now cheap — the implementation, the typing, the boilerplate. Everything upstream of the model — the noticing, the framing, the deciding — is where the leverage moved. Teams that keep optimizing for the old constraint (coordinating human labor through tickets and sprints) build overhead around the wrong bottleneck.
The founding reframe is one move: from a coordination tax to a coordination investment. Agile ceremony evaporates after each sprint — it is paid down, repeatedly. Coherence artifacts compound — they are paid forward, once. That single shift is the argument the discipline rests on.
Parallax sits above the stack as the shareable narrative surface. It composes the overhead view from the products' state — it does not own or contain them (sibling-over-parent-child is the architectural law here).
This is not a theory deck. It is a working system of composable products along one loop, and the loop ran on its own construction. Honest limit, adjudicated on the record: self-construction evidences that the system runs; it does not evidence that it generalizes. Agreement without displacement is cache. Generalization is exactly what the gates below exist to earn.
Intent is the reference implementation — the execution loop, proven first, with its own published site. The rest of the spine is the same discipline applied at other positions. That is the doorway: you arrive from Intent, and this is the system Intent is one instance of.
This is a synthesis, not a novel method. Each load-bearing idea is borrowed on purpose, and named — because the credibility comes with the name.
This is not yet a category; it is a hypothesis under pressure test. The discipline name — Coherence Engineering — is held internal on purpose, and only earns public use once three external-articulation gates clear. Until then the work speaks in its sibling vocabulary: prompt, context, and harness engineering.
And the honest market: the serviceable addressable audience today is roughly one — me. That is exactly why this surface exists. A worldview cannot advance past theory, or past an audience of its author, unless its view is expressable, navigable, and challengeable. So: navigate it, and challenge it.
Latest evidence the challenge is real: the altitude gate's first recorded runs (2026-07-19) failed the portfolio's own artifacts: the strategic root thread at 0.40 tension, the positioning doc at 0.00. The instrument refuses what it cannot verify, and the findings are open work, on the record.
The sharpest open question, stated plainly for the reader most likely to ask it: is the surface area too large? A product spine this wide is either coherence operationalized, or sprawl with a viewpoint name on top. If you'd implode part of it, that's the conversation this page is for.
Dunford's question: what are the real alternatives a collaborator has today, and why does none of them hold this position?
None holds altitude + coherence + narrative simultaneously. That intersection is the position — claimed as a hypothesis, not yet as a category.
Core/ECOSYSTEM-ARCHITECTURE-2026-05-20.mdCore/ECOSYSTEM-MARKETING-NARRATIVE-2026-05-20.mdCore/frameworks/coherence-engineering/DEFINITION.mdtheparlor.github.io/intent-site