An envelope-first language discipline: every safety claim explicit, scoped, inspectable, and mechanically accountable.
Panoply is not defined by a surface language, a family of faces, or a global claim of safety. It is defined by three artefacts:
-
a checked core — the Core into which every accepted program projects;
-
explicit evidence — the witnesses for the claims a program makes;
-
a safety-envelope manifest — the per-program statement of which guarantees have been earned and which have not.
Panoply’s central rule:
No guarantee without an envelope.
No envelope without evidence.
No composition without a composition rule.
Safety is scoped, inspectable, and parameterised by feature subset, projection, compiler mode, backend contract, and proof/check status — never asserted globally. Surface syntaxes are accountable projections (each must elaborate into Core + evidence + manifest), not "faces"; backends define their own contracts; experimental features may not borrow neighbours' claims.
Panoply is a narrowing of one lesson from AffineScript — that broad language surfaces need explicit trust envelopes — taken as a founding principle. It is not a rejection of AffineScript; AffineScript explores the surface, Panoply disciplines the claim.
The normative statement of all of the above is the charter:
-
docs/architecture/DESIGN-DISCIPLINE.adoc— the design discipline (charter). -
ADR-0002 — the decision adopting it.
Early. The charter is in place; the mechanisms it names — the Core checker, the evidence formats, the manifest schema, the per-backend contracts, and the projection-equivalence witnesses — are not yet implemented. Per the central rule, this repository asserts no guarantee it cannot yet witness. The repository ships the hyperpolymath standard scaffolding (CI/CD, machine-readable metadata, an AI-agent gatekeeper protocol, a typed ABI/FFI seam, and governance infrastructure) on which those mechanisms will be built.
| Path | What lives there |
|---|---|
|
The design discipline charter, topology, threat model. |
|
Architecture Decision Records. |
|
Universal entry point for AI agents (read first). |
|
Project metadata, policies, contractiles, AI configs. |
|
Source pillars (core, aspects, interface ABI/FFI, …). |
|
Proof scripts (Coq, Agda, Idris2) and verification harness. |
|
Task orchestration ( |
|
Workflows + community health files. |
|
Test suites and benchmarks. |
-
docs/architecture/DESIGN-DISCIPLINE.adoc— the charter (start here). -
EXPLAINME.adoc— how the scaffolding pieces map to real files. -
AUDIT.adoc— the release audit gate.
Released under the Mozilla Public License 2.0 unless a per-file
SPDX-License-Identifier says otherwise.