Phase-E — Publications (Static Index)
Governance Contract Summary
TRIZEL operates under strict layer separation principles:
- Layer-0 defines decisions only (trizel-core governance repository)
- Layer-1 produces evidence only (trizel-lab internal research)
- Layer-2 displays static references only (this site)
- Default = NO-GO unless explicitly allowlisted
- Human approval required for all publication additions
What Appears Here
This page lists publication-ready artifacts that have passed governance allowlisting. All entries are static references to immutable external resources.
No performance claims are made on this site. Publications are listed for reference purposes only, following strict governance protocols.
Publications Index
Data Source: This table mirrors entries from
phase-e/publications.yml. To add an item, update that file via PR
and manually copy the entry into this table.
| ID | Artifact Type | Immutable Link | Source | Verification Status |
|---|---|---|---|---|
|
No Phase-E publications are currently listed. Publications will appear here after governance approval and manual addition to the registry. |
||||
How to Add a Publication (Manual Process)
- Add candidate to allowlist in phase-e-gateway repository via PR
- Human review + approval of the allowlist entry
-
In this repository, update
phase-e/publications.ymlvia PR- Use the schema format from
TEMPLATE_PUBLICATION_ENTRY.txt - Only immutable URLs accepted (DOI/Zenodo/permalink/release tag)
- Use the schema format from
- Mirror the entry into the publications table above (copy/paste, no scripts)
- Human merge after review
Explicit Prohibitions
- No automatic publishing — All additions are manual
- No cross-repo writes from this site
- No mutable URLs — Branch URLs, latest release URLs, or non-versioned links are rejected
- Only immutable URLs accepted: DOI, Zenodo permalinks, tagged releases, institutional permalinks with version identifiers
Safety & Limitations
This Phase-E system is designed with strict safety constraints:
Explicitly Prohibited:
- No JavaScript — Zero client-side execution
- No fetch/runtime — No dynamic data loading
- No build process — No compilation or generation
- No counters — No view counts or visit tracking
- No analytics — No Google Analytics, no tracking pixels
- No dynamic charts — No runtime visualizations
- No external dependencies — No CDN fonts, no remote CSS
⚠️ Important: If a proposed change introduces any runtime behavior (scripts, fetch calls, build steps, or dynamic content), it must be rejected.
References
- Governance decision: See trizel-core decision record (reference only)
- Scientific Presentation Contract: View Contract
External links are provided as stable references only. No integration, no execution, no live data.