Scaffold Poke Discovery

The structural asymmetry between incoming and outgoing poke awareness

Theorem A.2·Poke Cone Asymmetry + Element V

A4A9A10T1B2Element-V

THE INSIGHT

Incoming pokes (errors, failures, complaints) are automatically sensed — they propagate through the contact graph and trigger adaptation (A10). Outgoing pokes (unused scaffold capabilities, unexplored API features, untried configurations) require deliberate exploration.

The organism's awareness of what its scaffold CAN do is strictly incomplete without active audit. You know what breaks. You do not know what you are not using.

This is the formal answer to: why do teams keep using 10% of a platform's features for years without discovering the rest?

Structural Poke Asymmetry

Theorem A.2 — Incoming vs. outgoing awareness

INCOMING POKE AWARENESS

When a poke arrives (A4: local disturbance from neighbor), the organism's loop network (Element III) detects the perturbation and propagates information about it through the contact graph. By A10 (adaptation required), survivors reorganize in response. Incoming poke awareness is automatic.

OUTGOING POKE AWARENESS

The scaffold the organism operates on (Element I) has capabilities the organism does not use. These unused capabilities are outgoing pokes that the organism could emit but does not. No incoming signal alerts the organism to their existence. Discovery requires deliberate exploration.

Corollary A.1

Exploration of the outgoing poke cone is strictly incomplete

Without deliberate exploration, the organism's knowledge of its scaffold's capability surface is bounded by the subset it has accidentally invoked. The unexplored region is not empty — it contains capabilities that could change the organism's architecture if discovered.

SCAFFOLD AUDIT TRIGGER (THEOREM C.1)

When a scaffold evolves (new API features, updated models, platform changes), the organism must re-explore. The audit is not optional — it is a selection pressure. An organism that does not re-audit after scaffold evolution is optimizing against a stale model of its own capabilities.

Cross-Domain Instances

SOFTWARE TEAMS

Use 10% of a platform's API for years. Only discover batch endpoints, webhooks, or streaming when a crisis forces exploration.

BIOLOGY

Organisms adapt quickly to incoming pathogens (immune response) but explore new metabolic pathways slowly (evolutionary timescale).

SCIENTIFIC RESEARCH

Anomalies in data (incoming pokes) trigger rapid investigation. Capabilities of unused instruments go undiscovered for decades.

STARTUPS

Bug reports arrive automatically. New platform features that could transform the product require deliberate discovery.

Falsifiable Predictions

Engineering

P1: Audit Adoption Speed

Teams that conduct periodic scaffold audits (quarterly review of platform capabilities) will adopt new features 3-5x faster than teams that only discover features through crisis response.

CONFIRMS IF

Audit-practicing teams adopt features 3-5x faster

FALSIFIES IF

No adoption speed difference between auditing and non-auditing teams

Engineering

P2: B_cx Debt Accumulation

After a scaffold evolution event (major API update), organisms that do not re-audit within one adaptation cycle will accumulate B_cx debt from workarounds that the new features would eliminate.

CONFIRMS IF

Non-auditing projects accumulate workaround B_cx debt

FALSIFIES IF

No measurable B_cx difference after platform updates

Source: Scaffold Poke Discovery formalization · Theorem A.2 (Structural Poke Asymmetry) + Corollary A.1 + Theorem C.1 (Scaffold Audit Trigger).