Universal Theories

Jump Through This Page

1. Purpose

Biology-Derived Membrane Triage identifies which constraint membrane failed first under compression.

It borrows structural logic from biological systems without reducing other domains to biology. In biology, membranes are not passive walls. They filter, regulate, transmit, protect, classify, exchange, and stabilize.

UTS generalizes this membrane logic across domains.

A membrane may appear as:

textScroll

cell membrane
immune classifier
blood-brain barrier
skin boundary
logistics pathway
API permission layer
AI tool boundary
institutional intake layer
appeal pathway
classification system
delivery channel
feedback loop
rollback layer
timing window

BDMT asks:

textScroll

Which membrane failed first under compression?

The answer matters because systems often repair the visible symptom instead of the first failed membrane.

The Constructs & Operating Systems Registry identifies Biology-Derived Membrane Triage as a diagnostic triage system that asks which constraint membrane failed first under compression.

2. Core Question

Which membrane failed first: boundary, classifier, delivery, damping, timing, or restoration?

Secondary questions:

Did the boundary fail first?
Did classification fail first?
Did delivery or routing fail first?
Did damping fail after perturbation?
Did timing collapse before action or repair?
Did feedback fail to return?
Did restoration target the symptom instead of the origin?
Which visible failure is downstream?
Which layer must be repaired first?
Is the cascade being misread?
Is the failure recurring because the first membrane remains unrepaired?

3. Construct Class

TableScroll

Field	Value
Construct Class	Diagnostic Triage System
Secondary Class	Membrane Failure / First-Failure / Cascade Mapper
Operating System	No
Primary Module	Biology / Medicine · AI Governance · Cybernetics
Related Modules	Restoration, Security, Coherence, Scaling, ISC

BDMT is a diagnostic triage system because it determines the first meaningful failure layer.

It is not a full biological theory. It is a cross-domain membrane diagnostic that uses biological pattern logic as a structural reference.

4. Canon Kernel

BDMT uses the following core triage kernels:

textScroll

E→B     Boundary failure
E→Γ     Classifier / evaluator failure
E→U0/G  Delivery / damping failure

Expanded:

TableScroll

Kernel	First Failure	Common Signs
E→B	Boundary failure	Scope creep, leakage, permission drift, unauthorized entry, forced coupling
E→Γ	Classifier / evaluator failure	Misclassification, reward hacking, evaluator capture, false positives / negatives
E→U0/G	Delivery / damping failure	Latency spirals, rollback failure, recovery failure, brittle response, poor settling

For broader UTS use, the membrane classes are:

textScroll

boundary membrane
classifier membrane
delivery membrane
damping membrane
timing membrane
restoration membrane

5. When to Use

Use Biology-Derived Membrane Triage when a system fails under pressure and the visible symptom may not be the first failure.

Use BDMT when:

a system is under compression
multiple failures appear at once
repair attempts keep missing the root
boundary, classifier, delivery, timing, or damping failures are entangled
an AI incident involves permissions, evaluation, routing, or rollback
an institution misclassifies cases and then fails delivery
a biological or medical analogy helps reveal first-failure logic
a security system blocks symptoms but not origin
a logistics system fails after classification or routing error
a platform response worsens because timing or damping failed
recurrence suggests the original membrane remains unrepaired
a cascade must be triaged before restoration can be sequenced

Do not use BDMT as the primary construct when the central question is:

TableScroll

If the question is...	Prefer...
What full membrane catalog applies?	Biology Membrane Atlas
Is the AI architecture repair-ready?	Repair-First AI Architecture
How should AI move to action?	AI Decision Pipeline
Is system variety sufficient?	Requisite Variety Checker
Did the system settle after disturbance?	Ring-Down / Damping Evaluator
Where is coherence lost in transmission?	CLSM
What restoration arc applies?	RAM

BDMT identifies the first failure membrane those constructs may then repair or expand.

6. Derivation

BDMT is derived from a recurring UTS pattern:

textScroll

system under compression
+ multiple symptoms appear
+ visible symptom is repaired first
+ first failed membrane remains unrepaired
= recurrence

A second pattern:

textScroll

boundary fails
+ classifier receives invalid inputs
+ delivery system routes wrong response
+ damping fails after overload
= cascade misread as runtime failure

A third pattern:

textScroll

classifier fails
+ correct boundary appears intact
+ wrong action is delivered confidently
+ restoration targets downstream harm
= evaluator failure hidden beneath execution

BDMT exists because first failure often hides upstream of visible failure.

Its core distinction is:

textScroll

visible symptom is not always first failure

7. UTS Basis

BDMT assembles the following UTS mechanics.

7.1 State Variables

TableScroll

Variable	Role in BDMT
O	Measures whether coherence is preserved after membrane stress.
H	Tracks hidden debt created by unrepaired membrane failure.
ε	Tracks error, noise, ambiguity, and classification uncertainty.
ι	Detects inversion where protective membranes become harmful.
Au	Measures traceability of failure sequence and membrane behavior.
µᵢ	Preserves meaning and functional integrity across classification and routing.
BΣ	Tracks boundary membrane integrity.
K	Tracks compatibility and fit between membranes, load, and response.
R	Measures restoration capacity after membrane failure.
Φ	Tracks load, pressure, force, compression, or amplification causing failure.

7.2 Primary U-Layer Pattern

BDMT most commonly localizes through:

textScroll

U0 → U2 → U4 → U3 → U5 → U7

Meaning:

textScroll

substrate
→ boundary
→ classifier
→ delivery / runtime
→ timing / damping
→ recurrence

This sequence helps identify where the first membrane failed and how the cascade propagated.

8. Inputs

8.1 Core Observational Inputs

TableScroll

Input	Description
System under compression	The biological, AI, institutional, security, technical, or social system being triaged.
Visible symptom	What failure is most obvious.
First observed failure	Earliest visible sign, even if not the true first failure.
Boundary behavior	Whether access, scope, permeability, or separation failed.
Classification behavior	Whether signals, cases, risks, or inputs were categorized correctly.
Delivery behavior	Whether the correct response reached the correct target.
Damping behavior	Whether perturbation settled, amplified, repeated, or hid as false calm.
Timing behavior	Whether response timing matched the phase and window.
Feedback behavior	Whether correction returned to the system.
Restoration response	What repair was attempted and at what layer.
Load condition	What pressure, compression, or throughput was applied.
Cascade sequence	How one failure led to another.
Recurrence pattern	Whether failure repeats after repair.
Domain translation	How biological membrane logic maps to the target domain.

8.2 Diagnostic Inputs

TableScroll

Diagnostic	What It Measures	Why It Matters
Boundary Integrity	Whether the boundary membrane held	Boundary failure often starts cascades.
Classifier Integrity	Whether the system categorized inputs or states correctly	Classifier failure produces wrong action.
Delivery Integrity	Whether response reached the right place in the right form	Delivery failure creates unresolved need.
Damping	Whether disturbance settled	Poor damping means restoration may be incomplete.
Timing Fit	Whether action matched phase	Wrong timing can invert repair.
Restoration Capacity	Whether repair can reach the failed layer	Prevents symptom-layer repair.
Membrane Permeability	Degree of filtering, leakage, or overblocking	Permeability failures can be too open or too closed.
Signal Specificity	Whether signals were precise enough for classification	Low specificity increases classifier failure.
Feedback Integrity	Whether correction reaches the membrane	Needed for adaptation.
Load Pressure	Compression applied to the system	High load reveals weak membranes.
Compression Load	Degree of complexity or pressure forced through membrane	Overcompression causes collapse.
Cascade Risk	Likelihood one membrane failure triggers others	Determines containment priority.
First Failure Layer	Earliest causal membrane failure	Core BDMT output.
Recurrence	Repetition after repair attempt	Shows whether origin was repaired.

9. Outputs

BDMT produces first-failure classification, cascade maps, and restoration sequencing.

9.1 Membrane Failure Assessment

Possible outputs:

textScroll

Boundary failed first
Classifier failed first
Delivery failed first
Damping failed first
Timing failed first
Restoration membrane failed first
First failure unclear
Multiple simultaneous membrane failures

9.2 Cascade Assessment

Possible outputs:

textScroll

No cascade detected
Cascade emerging
Cascade active
Cascade stabilized
Cascade misread
Cascade origin hidden
Cascade requires containment

9.3 Restoration Target Assessment

Possible outputs:

textScroll

Repair boundary first
Repair classifier first
Repair delivery first
Restore damping first
Repair timing first
Increase restoration capacity first
Contain cascade first
Run deeper triage
Origin-layer repair required

9.4 Decision Outputs

TableScroll

Output	Meaning
Repair boundary first	Boundary failure is primary or destabilizing.
Repair classifier first	Misclassification is upstream of visible failure.
Repair delivery pathway first	Correct signal/action is not reaching the target.
Restore damping first	Disturbance is not settling after intervention.
Repair timing first	Response is phase-misaligned.
Increase restoration capacity	Repair cannot reach failure layer.
Contain cascade	Secondary failures must be stabilized before full repair.
Run deeper triage	First failure cannot yet be identified.
Return ∅	No coherent restoration sequence exists under current observability.

10. Operating Logic

10.1 Basic Flow

textScroll

1. Identify system under compression.
2. Identify visible symptom.
3. Map earliest observable failure.
4. Check boundary membrane.
5. Check classifier membrane.
6. Check delivery membrane.
7. Check damping behavior.
8. Check timing fit.
9. Check restoration membrane.
10. Map cascade sequence.
11. Identify first failure layer.
12. Identify secondary failures.
13. Select first restoration target.
14. Validate over recurrence.

10.2 First-Failure Rule

textScroll

IF boundary failed before misclassification,
THEN repair boundary before classifier.

IF classifier failed before wrong delivery,
THEN repair classifier before delivery.

IF delivery failed while boundary and classifier were valid,
THEN repair routing / delivery path.

IF response was correct but disturbance did not settle,
THEN restore damping.

IF repair was correct but mistimed,
THEN recalibrate timing.

IF all repair targets miss,
THEN search for upstream membrane failure.

10.3 Symptom-Layer Warning

textScroll

Do not repair only the visible symptom unless the visible symptom is also the first failed membrane.

If recurrence continues after symptom repair,
the first failure layer was likely missed.

11. Operators Used

TableScroll

Operator	Role in BDMT
Ξ — Classification	Classifies membrane type, failure layer, cascade state, and restoration target.
Δ — Differentiation	Separates visible symptom from first failure, primary failure from secondary cascade.
Μ — Mapping	Maps membrane sequence, cascade path, and restoration order.
Π — Constraint / Scoping	Limits repair to the correct membrane and prevents overbroad intervention.
Λ — Compatibility	Tests fit between membrane function, system load, and repair path.
ℛ — Restoration	Repairs the first failed membrane and downstream cascade.
Σ — Integration / Coherence Binding	Reintegrates membrane functions into coherent operation.
Τ — Time Validation	Confirms recurrence reduces after first-failure repair.

12. Gates Required

TableScroll

Gate	Required Condition	Failure Result
BΣ validity	Boundary membrane is intact or explicitly identified as failed.	Boundary repair required.
Classifier Validity Gate	Classification membrane correctly identifies signal/state.	Classifier restoration required.
Delivery Integrity Gate	Response reaches correct target through correct path.	Delivery pathway restoration required.
Damping Gate	Disturbance settles after response.	Damping restoration required.
Timing Fit Gate	Response matches phase and window.	Timing recalibration required.
R sufficiency	Restoration capacity reaches the failed membrane.	Increase restoration capacity.
Au-Traceability	Failure sequence is traceable enough to triage.	Auditability restoration required.
Cascade Containment Gate	Secondary failures can be stabilized during repair.	Contain cascade before full restoration.
Τ validation	Repair reduces recurrence over time.	First-failure diagnosis remains provisional.

13. Failure Modes Detected

TableScroll

Failure Mode	Detection Signal
Boundary Failure	Scope, access, permeability, or separation fails first.
Classifier Failure	Inputs, signals, risks, or states are categorized incorrectly.
Delivery Failure	Correct response does not reach the correct target.
Damping Failure	Disturbance fails to settle after response.
Timing Failure	Response occurs too early, too late, or out of phase.
Cascade Misread	Secondary failure is mistaken for origin.
Symptom-Layer Repair	Visible symptom is repaired while first membrane remains broken.
Membrane Collapse	Multiple membrane functions fail under compression.
Permeability Inversion	Membrane becomes too open where it should filter, or too closed where it should allow.
Feedback Break	Correction does not return to the failed membrane.
Restoration Misdirection	Repair targets downstream symptom instead of first failure.
Compression Collapse	Load overwhelms membrane function.
Recurrence Without Origin Repair	Same pattern returns after apparent repair.
First-Failure Obscuration	Observability is too weak to locate origin layer.

14. Restoration Links

TableScroll

Restoration Arc	When Activated
Boundary Reconstitution	Boundary membrane fails first or destabilizes cascade.
Classifier Restoration	Misclassification is upstream of visible failure.
Delivery Pathway Restoration	Response cannot reach target correctly.
Damping Restoration	System does not settle after perturbation.
Timing Recalibration	Response is mistimed or phase-incoherent.
Origin-Layer Repair	First failure occurs upstream of visible symptoms.
Cascade Containment	Secondary failures must be stabilized during repair.
Feedback Restoration	Correction does not reach the failed membrane.
Slack Regeneration	Membrane lacks room to absorb load.
Recurrence Reduction	Repeated failure shows first membrane remains unrepaired.

15. U-Layer Localization

TableScroll

U-Layer	Relevance
U0 — Substrate	Biological, technical, physical, computational, or material membrane substrate.
U1 — Power / Budgets	Energy, resources, throughput, compute, staffing, or support available to membranes.
U2 — Configuration / Boundaries	Boundary membranes, permissions, interfaces, access limits, and permeability.
U3 — Execution / Runtime	Delivery, routing, response, actuation, or operational behavior.
U4 — Classification / Metrics	Classifier membrane, evaluator, immune logic, labels, categories, and risk classes.
U5 — Coordination / Time	Timing, phase, response latency, damping, and recovery windows.
U6 — Coherence Field	System-level coherence effects after membrane failure.
U7 — Memory / Recurrence	Repeated membrane failures, repair history, recurrence, and adaptation.
U8 — Environment / Forcing	Load pressure, pathogen/adversary pressure, market pressure, crisis, or environmental stress.

BDMT most commonly localizes through:

textScroll

U0 → U2 → U4 → U3 → U5 → U7

This means membrane triage begins with substrate, boundary, classifier, delivery, timing/damping, and recurrence.

16. Example Use Case

Scenario

An AI agent with tool access begins making incorrect updates to a shared database.

The visible symptom is wrong database entries. The team initially treats it as an execution bug.

BDMT checks the sequence and finds that the AI was allowed to access fields outside its intended scope. The classifier then interpreted those fields as editable. Delivery executed the wrong update.

BDMT Evaluation

The construct checks:

boundary behavior
classifier behavior
delivery behavior
rollback capacity
feedback loop
cascade sequence
first failure layer

Likely Findings

textScroll

Visible symptom: incorrect database entries
First failure: boundary membrane
Secondary failure: classifier membrane
Tertiary failure: delivery / execution
Restoration target: boundary first
Cascade risk: active

Recommended Output

textScroll

Do not repair only the database update logic.
Restrict field permissions first.
Repair classifier assumptions about editable fields.
Add dry-run and validation step.
Add rollback path.
Validate recurrence reduction over future updates.

Interpretation

The visible failure was execution, but the first failed membrane was boundary.

Repairing execution alone would leave the cascade path intact.

17. Anti-Patterns

Do not use BDMT to:

repair visible symptoms before finding first failure
assume execution failure is always runtime failure
ignore boundary conditions
treat classifier output as automatically valid
ignore delivery and routing paths
treat damping failure as successful suppression
repair downstream harm while origin membrane remains open
collapse all membrane failures into one category
over-translate biological analogies as literal identity
ignore recurrence after apparent repair
treat lack of observability as proof no upstream failure exists
repair timing before checking classifier and boundary
classify cascade order without auditability

18. Completion Criteria

A BDMT assessment is complete when:

system under compression is identified
visible symptom is identified
earliest observable failure is mapped
boundary membrane is checked
classifier membrane is checked
delivery membrane is checked
damping behavior is checked
timing fit is checked
restoration membrane is checked
cascade sequence is mapped
first failure layer is classified
secondary failures are identified
first restoration target is selected
recurrence validation is defined
∅ is returned if first failure cannot be coherently determined under current observability

19. Machine-Readable Summary

yamlScroll

construct_id: "CONSTRUCT-028"
title: "Biology-Derived Membrane Triage"
abbreviation: "BDMT"
type: "construct"
status: "draft-integrated"
construct_class: "Diagnostic Triage System"
operating_system: false
primary_module: "Biology / Medicine · AI Governance · Cybernetics"
related_modules:
  - "Restoration"
  - "Security"
  - "Coherence"
  - "Scaling"
  - "Interactions · Signals · Couplings"

core_question: "Which membrane failed first: boundary, classifier, delivery, damping, timing, or restoration?"

definition: "Biology-Derived Membrane Triage uses biology-derived membrane logic to identify the first failed constraint membrane under compression and sequence restoration accordingly."

canon_kernels:
  - "E→B: boundary failure"
  - "E→Γ: classifier / evaluator failure"
  - "E→U0/G: delivery / damping failure"

inputs:
  state_variables:
    - "O"
    - "H"
    - "ε"
    - "ι"
    - "Au"
    - "µᵢ"
    - "BΣ"
    - "K"
    - "R"
    - "Φ"
  diagnostics:
    - "Boundary Integrity"
    - "Classifier Integrity"
    - "Delivery Integrity"
    - "Damping"
    - "Timing Fit"
    - "Restoration Capacity"
    - "Membrane Permeability"
    - "Signal Specificity"
    - "Feedback Integrity"
    - "Load Pressure"
    - "Compression Load"
    - "Cascade Risk"
    - "First Failure Layer"
    - "Recurrence"
  gates:
    - "BΣ validity"
    - "Classifier Validity Gate"
    - "Delivery Integrity Gate"
    - "Damping Gate"
    - "Timing Fit Gate"
    - "R sufficiency"
    - "Au-Traceability"
    - "Cascade Containment Gate"
    - "Τ validation"
  observations:
    - "system under compression"
    - "visible symptom"
    - "first observed failure"
    - "boundary behavior"
    - "classification behavior"
    - "delivery behavior"
    - "damping behavior"
    - "timing behavior"
    - "feedback behavior"
    - "restoration response"
    - "load condition"
    - "cascade sequence"
    - "recurrence pattern"
    - "domain translation"

outputs:
  assessments:
    - "primary membrane failure"
    - "secondary membrane failures"
    - "cascade sequence"
    - "first restoration target"
    - "boundary status"
    - "classifier status"
    - "delivery status"
    - "damping status"
    - "timing status"
    - "restoration readiness"
  decisions:
    - "repair boundary first"
    - "repair classifier first"
    - "repair delivery pathway first"
    - "restore damping first"
    - "repair timing first"
    - "increase restoration capacity"
    - "contain cascade"
    - "run deeper triage"
    - "return ∅"
  maps:
    - "membrane failure map"
    - "first-failure map"
    - "cascade map"
    - "boundary failure map"
    - "classifier failure map"
    - "delivery failure map"
    - "damping failure map"
    - "restoration sequence map"

dependencies:
  operators:
    - "Ξ"
    - "Δ"
    - "Μ"
    - "Π"
    - "Λ"
    - "ℛ"
    - "Σ"
    - "Τ"
  failure_modes:
    - "Boundary Failure"
    - "Classifier Failure"
    - "Delivery Failure"
    - "Damping Failure"
    - "Timing Failure"
    - "Cascade Misread"
    - "Symptom-Layer Repair"
    - "Membrane Collapse"
    - "Permeability Inversion"
    - "Feedback Break"
    - "Restoration Misdirection"
    - "Compression Collapse"
    - "Recurrence Without Origin Repair"
    - "First-Failure Obscuration"
  restoration_arcs:
    - "Boundary Reconstitution"
    - "Classifier Restoration"
    - "Delivery Pathway Restoration"
    - "Damping Restoration"
    - "Timing Recalibration"
    - "Origin-Layer Repair"
    - "Cascade Containment"
    - "Feedback Restoration"
    - "Slack Regeneration"
    - "Recurrence Reduction"

u_layers:
  primary:
    - "U0"
    - "U2"
    - "U3"
    - "U4"
    - "U5"
    - "U7"
  secondary:
    - "U1"
    - "U6"
    - "U8"

null_outcome_allowed: true
visible_symptom_is_not_always_first_failure: true

20. Citation

Citation ID: construct-biology-derived-membrane-triage-v1-0

Recommended citation:

Universal Theory Stack. “CONSTRUCT-028 — Biology-Derived Membrane Triage.” UTS Constructs Registry, Version 1.0.0, 2026.

21. Summary

Biology-Derived Membrane Triage identifies which membrane failed first under compression.

Its core distinction is:

textScroll

visible symptom is not always first failure

BDMT maps whether the failure began at the boundary, classifier, delivery path, damping layer, timing window, or restoration membrane.

Its core logic is:

textScroll

Repair the first failed membrane before repairing downstream symptoms.

When the first failure cannot be determined, BDMT recommends deeper triage, cascade containment, auditability restoration, or:

textScroll

∅

BDMT gives UTS a first-failure diagnostic for systems under compression.

CONSTRUCT-027 — AI Decision Pipeline

Registry Tool Spec

CONSTRUCT-029 — Economic Circulation Framework