SIBurst

SIBurst Naming the phase change in intelligence.

SIBurst names a phase change in intelligence: the transition from incremental capability growth into a materially different operating regime.

SIBurst does not assert that superintelligence has been achieved, nor does it predict when or whether a specific transition will occur.

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

S0 QUIET ACCUMULATION

DEMONSTRATION STATE · S0 / ACCUMULATING

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

A system accumulates inside fixed rules.

Demonstration stage 1 of 7: accumulating. 3 entities sit in a lattice of 4 lanes and 6 cells per lane. Position follows arrival order, and each of the 2 relationships is drawn along the rails.

S1 SCALE

DEMONSTRATION STATE · S1 / DENSITY RISING

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

More entities. More relationships. The same rules.

Demonstration stage 2 of 7: density rising. 15 entities and 17 relationships occupy the same lattice under the same rules. Every relationship can still be routed along the rails.

S2 THRESHOLD

DEMONSTRATION STATE · S2 / THRESHOLD APPROACHING

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

Relationships begin to exceed the structure built to hold them.

Demonstration stage 3 of 7: threshold approaching. 22 entities nearly fill the lattice. 7 of the 29 relationships cannot be routed; each is shown as a stub that stops at the edge of its cell with a short cross mark. Every entity is still centred in its cell.

S3 INSTABILITY

DEMONSTRATION STATE · S3 / REGIME UNSTABLE

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

The old description fails in places.

Demonstration stage 4 of 7: regime unstable. All 24 entities are present. 17 of the 41 relationships cannot be routed, and entities with unrouted relationships have slipped from the centres of their cells toward them. The rails are unchanged and the lattice rules still apply.

S4 PHASE CHANGE

DEMONSTRATION STATE · S4 / TRANSITION DETECTED

Rules in force: the lattice at the end of S3.
Rules changed: the same entities, placed by their relationships.

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

The rules change. The entities remain.

Demonstration stage 5 of 7: transition detected. The rails retire. The same 24 entities move from lattice positions to positions set by their relationships, and every stub resolves into its full relationship. No entity or relationship is added or removed. Anchors N08 and N09, neighbours in the lattice, separate; anchors N05 and N19, at opposite corners of the lattice, come together.

S5 SIBURST

DEMONSTRATION STATE · S5 / SIBURST

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

SIBurst names this crossing: from more capability to a different operating regime.

Demonstration stage 6 of 7: SIBurst. The field is stable. The transition record compares the end of the lattice with the field: the same 24 entities and the same anchors, organized by different rules.

Transition record

Lattice · end of S3

Field · S5

Left: the lattice at the end of S3, with 24 entities placed by arrival order and 17 relationships it cannot route. Right: the field, with the same 24 entities placed by their relationships and all 41 relationships drawn. Anchors N08 and N09 are neighbours in the lattice and separate in the field. Anchors N05 and N19 are at opposite corners of the lattice and come together in the field. Anchors: N05, N08, N09, N19.

S6 THE AFTER

DEMONSTRATION STATE · S6 / NEW OPERATING REGIME

SYSTEM DEMONSTRATION — a model of the SIBurst concept, not a measurement.

SIBurst names the transition, not the prediction.

Demonstration stage 7 of 7: new operating regime. The field recedes and the reference layer opens. The demonstration ends here and does not restart.

Enter the reference layer

Reference

The governed doctrine behind the demonstration. Each page is generated from its canonical Markdown source.

Reference Field

A map of the 15 canonical documents, drawn in the Field grammar. It is not part of the demonstration system. Each of the 51 links exists because one document names the other's source file (DEC-025). The same documents and their explicit references are listed in reading order in the reference layer.

Conceptual foundation

  • FOUNDATION_THESIS.mdThe intellectual core: accumulation, threshold, discontinuity, new operating regime.Explicit references: COMMERCIAL_TERRITORY.md, PUBLIC_CLAIM_POLICY.md, INTERFACE_CONTRACT.md, SITE_BUILD.md
  • NAME_ARCHITECTURE.mdCanonical semantics of SI, Burst, and SIBurst, in semantic, temporal, and commercial layers.Explicit references: CATEGORY_BOUNDARY.md, COMMERCIAL_TERRITORY.md, GLOSSARY.md, PUBLIC_CLAIM_POLICY.md, DECISION_LOG.md, INTERFACE_CONTRACT.md
  • CATEGORY_BOUNDARY.mdWhat SIBurst is not by default, its natural territory, and the boundary test.Explicit references: NAME_ARCHITECTURE.md, COMMERCIAL_TERRITORY.md, PUBLIC_CLAIM_POLICY.md, DECISION_LOG.md, INTERFACE_CONTRACT.md
  • COMMERCIAL_TERRITORY.mdPublic map of application areas: Build, Act, Measure, Cross.Explicit references: FOUNDATION_THESIS.md, NAME_ARCHITECTURE.md, CATEGORY_BOUNDARY.md, GLOSSARY.md, PUBLIC_CLAIM_POLICY.md, DECISION_LOG.md, INTERFACE_CONTRACT.md
  • GLOSSARY.mdGoverned definitions of the project's working vocabulary.Explicit references: NAME_ARCHITECTURE.md, COMMERCIAL_TERRITORY.md, PUBLIC_CLAIM_POLICY.md, INTERFACE_CONTRACT.md
  • PUBLIC_CLAIM_POLICY.mdClaim classes, prohibited claims, and the standard every public statement must meet.Explicit references: FOUNDATION_THESIS.md, NAME_ARCHITECTURE.md, CATEGORY_BOUNDARY.md, COMMERCIAL_TERRITORY.md, GLOSSARY.md, SITE_ARCHITECTURE.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, INTERFACE_ACCEPTANCE.md, DEMONSTRATION_FIXTURE.md
  • SITE_ARCHITECTURE.mdConceptual design of the future interface: the seven-stage experience and its prohibitions.Explicit references: PUBLIC_CLAIM_POLICY.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, VISUAL_SYSTEM.md, MOTION_SEMANTICS.md, RESPONSIVE_ACCESSIBILITY.md, INTERFACE_ACCEPTANCE.md
  • DECISION_LOG.mdDurable record of decisions and their consequences.Explicit references: NAME_ARCHITECTURE.md, CATEGORY_BOUNDARY.md, COMMERCIAL_TERRITORY.md, PUBLIC_CLAIM_POLICY.md, SITE_ARCHITECTURE.md, INTERFACE_CONTRACT.md, VISUAL_SYSTEM.md, MOTION_SEMANTICS.md, RESPONSIVE_ACCESSIBILITY.md, INTERFACE_ACCEPTANCE.md, DEMONSTRATION_FIXTURE.md, SITE_BUILD.md

Implementation doctrine

  • INTERFACE_CONTRACT.mdThe implementation contract: seven-stage state machine, Lattice-to-Field rule change, semantic primitives, scoped state language, progress, content and reference architecture, and implementation constraints.Explicit references: FOUNDATION_THESIS.md, NAME_ARCHITECTURE.md, CATEGORY_BOUNDARY.md, COMMERCIAL_TERRITORY.md, GLOSSARY.md, PUBLIC_CLAIM_POLICY.md, SITE_ARCHITECTURE.md, DECISION_LOG.md, VISUAL_SYSTEM.md, MOTION_SEMANTICS.md, RESPONSIVE_ACCESSIBILITY.md, INTERFACE_ACCEPTANCE.md, DEMONSTRATION_FIXTURE.md, SITE_BUILD.md
  • VISUAL_SYSTEM.mdSpatial character, semantic color and typography roles, and density progression.Explicit references: SITE_ARCHITECTURE.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, RESPONSIVE_ACCESSIBILITY.md, INTERFACE_ACCEPTANCE.md, SITE_BUILD.md
  • MOTION_SEMANTICS.mdThe permitted motion classes and the reduced-motion path.Explicit references: SITE_ARCHITECTURE.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, RESPONSIVE_ACCESSIBILITY.md, INTERFACE_ACCEPTANCE.md
  • RESPONSIVE_ACCESSIBILITY.mdBehavior across viewports and input methods, and WCAG 2.2 AA requirements.Explicit references: SITE_ARCHITECTURE.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, VISUAL_SYSTEM.md, MOTION_SEMANTICS.md, INTERFACE_ACCEPTANCE.md, DEMONSTRATION_FIXTURE.md
  • INTERFACE_ACCEPTANCE.mdGate 0 (fixture integrity) and the pass/fail tests every implementation must meet.Explicit references: PUBLIC_CLAIM_POLICY.md, SITE_ARCHITECTURE.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, VISUAL_SYSTEM.md, MOTION_SEMANTICS.md, RESPONSIVE_ACCESSIBILITY.md
  • DEMONSTRATION_FIXTURE.mdThe laws of the canonical demonstration system: arrival, placement, routing, stubs, S3 offsets, clusters, anchors, Field geometry, viewports.Explicit references: PUBLIC_CLAIM_POLICY.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, RESPONSIVE_ACCESSIBILITY.md
  • SITE_BUILD.mdHow the static interface is built, checked, and validated: sources, deterministic build, reference generation, runtime constraints.Explicit references: FOUNDATION_THESIS.md, DECISION_LOG.md, INTERFACE_CONTRACT.md, VISUAL_SYSTEM.md

Reference index