Ledger above ego
Important decisions, claims, changes, and failures should leave inspectable receipts.
Field constitution · coordinate 08
Wonder with edges.
These principles are not marketing promises. They are design constraints used to judge what belongs in the portal and how it should behave.
06operating principles
Working constitution
How the Field should hold people.
Every project may express these principles differently, but none should quietly contradict them.
Human authority remains explicit
Computational Collaborators may assist, propose, model, and challenge. They do not silently acquire human mandate.
Consent before expansion
A system should not increase scope, collect more information, or deepen dependency without a clear reason and meaningful choice.
Wonder needs boundaries
Imagination is welcomed. Research claims, operational demonstrations, creative works, and hypotheses remain visibly distinct.
Exit is part of the architecture
People should be able to pause, leave, export, refuse, or choose a quieter path without punishment.
Repair beats performance
When a system fails, the priority is containment, explanation, restoration, and learning—not defending appearances.
Publication boundary
What this portal does not prove.
- 01
A project room does not prove that the project is finished, safe for deployment, commercially available, or scientifically validated.
- 02
Generated diagrams, field cards, and conceptual models are not substitutes for prototypes, measurements, independent review, or regulatory approval.
- 03
Wellness and reflective experiences are not medical diagnosis, treatment, crisis care, or a replacement for qualified human support.
- 04
Public ledger entries are curated continuity receipts, not production telemetry or a cryptographic guarantee unless a room explicitly demonstrates those properties.