Systems that
hold pressure.

JUNCTION-FINDER.js
SCROLL ↓
00 — Intro
All in. One integrity out.

The client brings what they have — context, constraints, raw material. CONDUIT assembles it into one system that identifies itself, accepts growth, and outlives trends.

Method Three phases, one outcome
Output One justified system, plain-text docs
Scale By complexity, not by hours
Direct contact
01 — Selected work

Recent work.

W1
DETATECH
Identity system, hardware UI, applied production
2024
→
W2
VENA
Platform identity, primitives, interface
2024
→
W3
CONDUIT
Self-applied protocol
2026
→
02 — Principle

Three properties. One system.

One system, hyper-connected enough to hold three properties at once. Each property is a criterion of sufficiency — not a feature, not a style. The system is sized to satisfy them. Nothing more.

i.
Always identifies itself
On any carrier, in any context, the system is recognizable without explanation. Identity is a property of the system, not of a logo placed on top.
ii.
Always accepts growth
Modules can be added. Carriers can be changed. The system absorbs new applications without rewriting itself. Rules scale; they don't break.
iii.
Outlives trends
Value comes from structural connection to the project, not from a current visual moment. The system holds in five years because it was never tied to one.
The system is the brand. Not packaging around it.
03 — Protocol

Three phases.

Every project moves through the same three phases. Each phase produces a document. Each document grounds the next phase.

04 — System

Protocol deliverables.

Six modules. What gets handed over at the end of the protocol. A technical specification with examples and source files.

System Map
The reasoning document. Every decision in the system points back here. The map is where the system can be argued with.
Wordmark / Mark
Constructed on the grid. Ratios, spacing, exclusion zones, applied behavior across carriers.
Typography System
Scale, hierarchy, line-height, token map. Type as a parameter of the system, not a decorative choice.
Grid System
Base unit, columns, breakpoints. The geometry beneath every applied piece. Same logic, different carriers.
SVG Primitives
The minimal set of shapes the system is allowed to make. Every applied piece is composed from these.
Rule Set
Operational, scaling and exception rules. Optimizes decision-making after handover. Every rule testable in use.
05 — Boundaries

What the protocol does not do.

Four things, stated plainly. They aren't preferences. They're conditions for the protocol to work at all.

—
No many options
CONDUIT returns one justified solution, derived from the parameters of the system. If the solution does not fit, the parameters are revised — not the solution.
—
No marketing
Honest decisions on real circumstances. No persuasion layer, no narrative wrapping. The system speaks for itself or it is wrong.
—
No lying
Form follows function. If a decision cannot be justified from the map, it is removed. No decoration disguised as meaning.
—
No over-building
No component, rule or token exists without a reason in the system. The protocol stops at sufficiency, not at completeness.
06 — Scale

Sized by complexity.

Complexity is measured by three things: number of unknowns at intake, number of rules required to resolve them, number of carriers the system must reach.

C1 Contained
UnknownsFew
RulesContained set
CarriersOne to two
Timeline1–3 weeks
Compact system — map, core, single applied surface.
C2 Modular
UnknownsModerate
RulesModular set
CarriersThree to five
Timeline4–6 weeks
Working system across multiple carriers with shared logic.
C3 Extended
UnknownsHigh
RulesScalable
CarriersMulti-channel
Timeline8–12 weeks
Full identity with extended application and scaling rules.
C4 Open
UnknownsOpen scope
RulesResearched
CarriersPer scope
TimelineUp to 6 months
Research protocol, system prototype, long-form project.
Payment50% to start, 50% on delivery
UnitComplexity. Never hours.
RevisionsTwo rounds, on functional grounds
DocumentationTechnical spec with examples
07 — Rules

Behavior of the protocol.

Ten rules. They describe how decisions are made inside the system, not how things look. Select a rule to inspect.

FORM

Form exists only as consequence of function or intent.

TRIGGER A visual decision is proposed without a stated reason.
ACTION Trace it back to a function or an intent in the system map.
OUTCOME If the trace fails, the decision is removed. No decoration disguised as meaning.
08 — Contact

Direct line.

Manual intake. Type only inside the bracketed slots. Response within 48h.

Email [ ]
Project [ ]
Brief [ ]
State [ ]
Surface [ ]
Timeline [ ]
Links [ ]