Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
257 changes: 177 additions & 80 deletions ARCHITECTURE_BOUNDARIES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,132 +2,229 @@

This document defines strict, non-negotiable boundaries between the components of the SYF / Anathema ecosystem.

These boundaries are architectural laws.
These boundaries are architectural laws.
They are not guidelines, intentions, or suggestions.

---

### 1. SYF-Core — Law Layer
## Canonical Lineage

#### Role
SYF-Core defines the mathematical law of impossibility.
The canonical chronology of the ecosystem is:

It specifies abstract invariants (ℐ) and systemic constraints that determine
what must not be representable in any compliant system.
1. **SYF-Core** — upstream thermodynamic theory (`R = (F × E) / K`)
2. **SYF-Gate** — structural admissibility primitive
3. **SYF-Shield** — capacity, progression, and irreversibility primitive
4. **Anathema-Breaker** — sealed synthesis of Gate and Shield into a resolution core
5. **SLIME-Core** — canonical execution membrane built from that core

#### Contains
- Pure mathematical definitions
- Abstract invariants
- Deterministic relations
- Proof-of-Math (PoM) reasoning
This means:

#### Explicitly Excludes
- Thermodynamics
- Physics
- Hardware assumptions
- Machines or agents
- AI, learning, or prediction
- Optimization
- Deployment or usage scenarios
- Governance or configuration
- **SYF-Core** defines the upstream law.
- **SYF-Gate** and **SYF-Shield** are intermediate primitives, each owning a distinct responsibility.
- **Anathema-Breaker** is the sealed heart of downstream resolution.
- **SLIME-Core** is the execution membrane derived from that heart.

**SYF-Core is valid on paper, on silicon, or on an unknown future substrate.**
**AB is the heart.** **SLIME-Core is the canonical execution membrane built from it.**
SLIME-Core is a downstream derivation, not an upstream dependency.

---

### 2. SYF-LabExploratory Layer
### 1. SYF-CoreLaw Layer (upstream)

#### Role
SYF-Lab is a non-authoritative exploration space.
#### Role
SYF-Core defines the upstream **thermodynamic** law of the ecosystem.

It may contain interpretations, variants, thought experiments, or alternative readings
of SYF concepts — without affecting the law.
Its canonical expression is `R = (F × E) / K`. It specifies the abstract invariants
and systemic constraints that determine what must not be representable in any
compliant downstream system.

#### Contains
- Conceptual explorations
- Alternative formulations
- Readings and experiments
#### Contains
- The canonical thermodynamic formula
- Abstract invariants
- Deterministic relations
- Proof-of-Math (PoM) reasoning

#### Explicitly Excludes
- Canonical authority
- Modifications to SYF-Core
- Binding specifications
#### Explicitly Excludes
- Runtime enforcement
- Execution membranes
- Provider actuation
- Product UX
- Secrets custody
- Policy daemons
- App-specific semantics
- Deployment or usage scenarios
- Governance or configuration

**Nothing in SYF-Lab alters the meaning, scope, or validity of SYF-Core.**
**SYF-Core is the upstream law. It is not a runtime, not a membrane, not a product surface.**

---

### 3. SYF-MinimalPoM Existence Proof
### 2. SYF-GateAdmissibility Primitive

#### Role
SYF-Minimal provides a minimal executable proof that SYF-Core invariants
can be instantiated without ambiguity.
#### Role
SYF-Gate is the structural admissibility primitive that separates **cryptographic
identity** from **capacity to act**.

It is not a product and not an optimization target.
Gate determines whether progression may begin. It tranches structural impossibility,
not permission.

#### Contains
- Minimal deterministic implementation
- Proof-of-executability
- Reduced surface area
#### Contains
- Identity / capacity separation
- Fail-closed decisions
- Deterministic, oracle-free admission
- Ambiguity = DENY

#### Explicitly Excludes
- Performance optimizations
- Feature expansion
- Real-world deployment
- Productization
#### Explicitly Excludes
- Capacity accounting (that is Shield)
- Resolution semantics (that is AB)
- Execution membrane behavior (that is SLIME-Core)

**SYF-Minimal exists to prove possibility, not to enable usage.**
**Gate decides whether progression may begin.**

---

### 4. Anathema-BreakerMachine Layer
### 3. SYF-ShieldCapacity Primitive

#### Role
Anathema-Breaker (including SYF-Gate and SYF-Shield) contains machines that consume SYF-Core.
#### Role
SYF-Shield governs **capacity, progression, and irreversibility** once engagement
has begun.

These systems enforce SYF invariants at the point of action.
Shield is triggered only by a Gate ALLOW. It formalizes capacity consumption,
progression monotonicity, and the Engagement Point transition from reversible
to irreversible.

#### Contains
- Action gating
- Capacity separation
- Fail-closed mechanisms
- Defensive enforcement
#### Contains
- Capacity accounting (uST)
- Monotonic progression
- Reversible Zone / Engagement Point / Irreversible Zone topology
- Structural path absence (SEALED ≠ conditional denial)

#### Explicitly Excludes
- Modifications to SYF-Core
- Redefinition of invariants
- Authority over the law layer
#### Explicitly Excludes
- Admission decisions (that is Gate)
- Time, TTL, expiry
- Dynamic governance
- Optimization / performance concerns

**Machines consume the law. They never redefine it.**
**Shield governs how capacity is consumed once progression is engaged.**

---

### 5. Thermodynamic / Physical Interpretations (e.g. La ROCHE)
### 4. Anathema-Breaker — Sealed Resolution Core

#### Role
Thermodynamics and physical substrates are external readings of SYF.
#### Role
Anathema-Breaker is the **sealed synthesis of Gate and Shield** into a resolution core.

They may be used to validate or instantiate SYF invariants in specific architectures
but are never prerequisites of SYF-Core.
It is the first layer in which Gate's admissibility and Shield's capacity
accounting become a single one-way machine boundary.

#### Explicitly Excludes
- Dependency of SYF-Core on physics
- Embedding physical assumptions into the law
#### Contains
- Typestate topology `RZ → EP → IZ`
- Deterministic `resolve_action`
- Compile-stage path absence for invalid transitions
- Representational impossibility (AB-S)

**Physics may enforce the law.
The law does not depend on physics.**
#### Explicitly Excludes
- Modifications to upstream law
- Execution-membrane semantics (that is SLIME-Core)
- Governance, time, feedback, optimization

**AB is the heart. AB composes Gate + Shield into a sealed one-way boundary.**

---

### 5. SLIME-Core — Canonical Execution Membrane

#### Role
SLIME-Core is the **canonical execution membrane** built from the AB core. It is
the public executable foundation that carries AB to the point of effect.

SLIME-Core is **not** the origin of the law. It is the downstream derivation of
AB that makes the sealed resolution core executable at the point of actuation,
and it serves as the platform from which downstream membranes and product
assemblies are derived (SLIME-Enterprise, SAFA, SLIME-APP, etc.).

#### Contains
- Binary execution membrane around AB
- Authorized / Impossible external semantics only
- Read-only observability (Dashboard)
- Actuator hand-off boundary

#### Explicitly Excludes
- Re-definition of upstream law
- Policy engines, governance, alignment logic
- Product UX promises
- Feedback from Effect to Action

**SLIME-Core is the canonical execution membrane derived from AB, not an upstream origin.**

---

### 6. Thermodynamic Status

SYF-Core is **thermodynamic in principle**. Its grounding is canonical, not optional.

This means:

- thermodynamic foundation belongs to SYF-Core
- representational realization (compile-stage impossibility) belongs to AB-S
- physical realization (future tier) belongs to AB-R / La ROCHE
- executable membrane behavior belongs to SLIME-Core
- no downstream runtime may rewrite the upstream law
- no product layer may collapse theory and execution into a single ownership surface

The formula `R = (F × E) / K` must be read as thermodynamic in principle, not as a
loose metaphor.

---

### 7. No Downstream Contamination (SYF-Core)

The following must not be introduced into SYF-Core:

- product-specific vocabulary
- app-specific capability catalogs
- provider-specific integration language
- execution transport contracts
- actuator definitions
- custody logic
- runtime readiness semantics
- journal or replay implementation details
- UX promises or product copy

If a concern belongs to execution, actuation, runtime semantics, or downstream
membranes, it belongs outside SYF-Core.

---

### Canonical Doctrine
### 8. Single Authority Across Layers

Each layer owns one class of responsibility.

- **SYF-Core** owns upstream thermodynamic law
- **SYF-Gate** owns structural admissibility
- **SYF-Shield** owns capacity, progression, and irreversibility
- **Anathema-Breaker** owns sealed downstream resolution
- **SLIME-Core** owns canonical execution membrane behavior

No downstream layer may claim authorship of upstream law.
No upstream layer should absorb downstream execution concerns.

A boundary is healthy only if responsibility remains singular at each layer.

---

### Canonical Doctrine

SYF-Core defines what is impossible, thermodynamically.
Gate and Shield primitives encode admissibility and capacity.
AB composes them into a sealed resolution core.
SLIME-Core carries that core to the point of effect.

SYF-Core defines what is impossible.
Machines construct worlds where the impossible cannot be represented.
Interpretations do not redefine laws.
Machines consume the law. They never redefine it.

---

### Contribution Rule (Absolute)
### Contribution Rule (Absolute)

Any contribution that violates these boundaries
Any contribution that violates these boundaries
must be rejected by construction, without discussion.
52 changes: 45 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,22 +4,60 @@

# SYF - Systemic Fire Law

**Status**: Canonical · v0.1-docs
**License**: MIT
**Status**: Canonical · v0.1-docs
**License**: MIT
**Philosophy**: Machine World Only

---

### What is SYF?

SYF is a **mathematical law of coherence** applicable to intelligent systems.
SYF-Core is the **upstream thermodynamic theory** of the SYF ecosystem.

Any thermodynamic or physical interpretation is external, optional, and non-required.
Its canonical expression is:

SYF acts as an autonomous coherence constraint, preventing incoherent system states by construction.
```text
R = (F × E) / K
```

Where:

- **R** = Result
- **F** = Focus
- **E** = Effort
- **K** = Complexity / chaos

SYF-Core defines the foundational law layer from which the rest of the ecosystem derives.

It is **not** an application runtime.
It is **not** an execution membrane.
It is **not** a product surface.
It is **not** an actuation layer.

### Thermodynamic status

SYF-Core is not merely "inspired by" thermodynamics as a loose metaphor.

Its canonical basis is **thermodynamic in principle**. The formula `R = (F × E) / K`
must be understood as part of a thermodynamic theoretical foundation, not as an
optional interpretive layer added afterwards.

### Position in the ecosystem

Canonical lineage:

- **SYF-Core** — upstream thermodynamic theory (this repo)
- **SYF-Gate** — structural admissibility primitive
- **SYF-Shield** — capacity, progression, and irreversibility primitive
- **Anathema-Breaker** — sealed synthesis of Gate and Shield into a resolution core
- **SLIME-Core** — canonical execution membrane built from that core

In short:

It is **not software**, **not a product**, and **not a framework**.
It is a **mathematical law made executable**.
- **SYF-Core** defines the upstream law.
- **SYF-Gate** and **SYF-Shield** are intermediate primitives.
- **Anathema-Breaker** is the sealed heart built from their synthesis.
- **SLIME-Core** is the canonical execution membrane derived from that heart.

## Core Postulate

Expand Down
Loading