Collaboration is the substrate condition in which two agents maintain stable orientation toward the same attract long enough for the system to guarantee, coherent, joint action

Frame

edge

Substrate

Filter gradient lighting

Orientation

Gradient

Collaboration

Good question. This is architectural, not aesthetic.

Let’s reason together

Each implies a different ontological status.

Micro = diagnostic / logic / calibration layer.

Bushing operates before content logic.

It is not a diagnostic of truth.

It is a diagnostic of frame.

Micro monitors internal consistency.

Bushing monitors relational tolerance.

Different layers.

If It Lives in Basis

Basis = structural primitives.

Substrate-level invariants.

Pre-semantic mechanics.

Bushing:

• Is pre-interpretive.

• Is geometry-bound.

• Is tolerance-based.

• Operates before meaning formation.

That makes it a Basis primitive, not a domain module.

It belongs alongside:

• Substrate

• Edge

• Gradient

• RP

Not inside Loom.

Not inside Micro.

Clean Placement Decision

Bushing is a Basis-level Relational Interface Primitive.

It should not be owned by Loom or Micro.

Instead:

Basis

→ defines RP

→ defines Bushing

→ Loom consumes RP outputs

→ Micro audits post-formation logic

That preserves separation of concerns.

Why This Matters

If you put Bushing in Loom:

You risk aestheticizing it.

If you put it in Micro:

You risk computationalizing it.

If you keep it in Basis:

It remains structural and neutral.

And given your recurring concern about authority creep,

keeping Bushing at Basis prevents it from becoming enforcement.

Final Answer

It goes in Basis.

Loom uses it.

Micro may read its state.

But it lives in Basis.

That keeps the machine clean.

No cross-contamination.