PAPER
SERVICE CONTRACT · VIEW: GOV
Axiom
PAPER is the research publishing lane. Every manuscript is a PROOF artifact — authored in markdown, compiled through the MAGIC pipeline, peer-review gated, and surfaced with citation governance. The academic voice of governed infrastructure.
Constraints
MUST: Evidence every claim with citation or data reference MUST: Cite clinical transcript IDFs (MAMMOCHAT CHAT lane) as research evidence where applicable MUST: Declare co-authors in front matter (mapped to USER principals) MUST: Compile through MAGIC pipeline — XeLaTeX backend for PDF MUST: Pre-publication drafts are VAULT-gated (PRIVATE until published) MUST: Ledger publish events (authors, title, submission date, commit hash) MUST: Every child instance at PAPERS/ inherits these constraints MUST: All citation codes resolve to BIBLIOGRAPHY.md sources on every surface (WEB hyperlink, TEX/PDF bibliography entry) MUST: Citation hyperlinks open source in new tab (target="_blank") — never steal focus from the reading surface MUST: PDF compiles to 2-column academic format (article class) — no 1-column drift MUST: Tri-view (gov | web | tex) with zero markdown leak — all syntax resolves to native format per surface MUST NOT: Publish without all co-author acknowledgements MUST NOT: Publish private or pre-publication content on public surface MUST NOT: Hand-author compiled outputs MUST NOT: Bypass build pipeline MUST NOT: Pass raw citation codes or markdown syntax to any rendered surface
Capabilities
CITATION_EVIDENCE, MANUSCRIPT_COMPILE, PROOF_EMIT, XELATEX_EMIT
COVERAGE: 255/255
SPEC
Purpose
PAPER is the research publishing lane.
Every research paper, clinical study, and technical manuscript is a PROOF artifact — authored in markdown, compiled through the MAGIC pipeline, and surfaced on the governed frontend. PAPER shares the publishing contract with BLOG, BOOK, and DECK but enforces peer-review gates and citation governance.
Structure
Leaf SERVICE scope. No governed child scopes.
Paper content lives in {USER}/PAPERS/ (instance scope, SHOP.md projection).
Instance follows the Instance Pattern at {USER}/PAPERS/.
Required closure artifacts per scope:
CANON.md, README.md, PAPER.md, VOCAB.md, ROADMAP.md, COVERAGE.md, LEARNING.md.
Learning lane per governed scope:
LEARNING.md at the scope root is terminal and SHALL NOT nest further LEARNING/.
Routes
web_docs: https://hadleylab.org/
web_surface: https://hadleylab.org/SERVICES/PAPER/
web_app: https://hadleylab.org/PAPERS/
magic: magic://hadleylab.org/PAPERS/
Surface
layout: paper <- _layouts/paper.html (academic format)
body: paper-page <- CSS class, single-col HTML (PDF is 2-col)
template: paper.latex <- XeLaTeX article class, 2-col, abstract, citations
view: gov | web | tex <- tri-view: GOV contract + WEB prose + TEX PDF.js canvas
Publishing Contract
1. Author writes {PAPER}.md in {USER}/PAPERS/{TITLE}/
2. Front matter declares: title, authors, date, scope, tags, doi (if published)
3. Build pipeline compiles to governed HTML with citation formatting
4. SHOP.md projection emits public-safe metadata (title, authors, abstract, date)
5. Full paper available at PAPERS/ surface (auth-gated if pre-publication)
6. Published artifacts are deterministic — same source = same output
7. LATEX backend compiles via paper.latex (article class, 2-col, citations)
8. PDF artifact available via pdf: front matter field and download dropdown
Peer Review Gates
MUST: Declare co-authors in front matter (mapped to USER principals)
MUST: Evidence every claim with citation or data reference
MUST: Pre-publication drafts are VAULT-gated (PRIVATE until published)
MUST NOT: Publish without all co-author acknowledgements
Ecosystem Connectivity
- Upstream:
SERVICESgovernance contracts andhadleylab-canonicscope inheritance. - Runtime: Jekyll compilation via
remote_theme— governed markdown to formatted research HTML. - Frontend: PAPERS/ surface compiled to governed SPA route. SHOP-safe abstracts in catalog.
- Ledger plane: publish events ledgered (authors, title, submission date, commit hash).
Pages
| Page | Sections |
|---|---|
| Overview | Purpose, Structure |
| Publishing | Routes, Publishing Contract, Peer Review Gates |
| Ecosystem | Ecosystem Connectivity |
Default: Overview.
Instance Pattern
{USER}/PAPERS/
PAPERS.md <- instance spec
CANON.md <- scope governance
SHOP.md <- public projection
COVERAGE.md <- compliance
LEARNING.md <- learning trail
README.md <- scope readme
ROADMAP.md <- scope roadmap
VOCAB.md <- scope vocabulary
INTEL
Research Portfolio
| Paper | Domain | Status | Evidence |
|---|---|---|---|
| STARGEO | Gene expression meta-analysis | Published | NIH BD2K $634K |
| MammoChat | Breast health AI chatbot | Active trial | FDOH $2M, NCT06604078 |
| CrADLe | Clinical NLP | Active trial | NIH/NLM $1.6M, NCT05384912 |
| BACPAC REACH | Spine outcomes | Active consortium | NIH/NIAMS $30M, NCT06631105 |
| MAGIC compliance 255 | Governance language system | Pre-print | 6 provisionals filed |
| Wound Paper (255B) | Clinical wound assessment | VAULT-gated | INTEL.md bridge to FORECASTS |
Citation Network
| Source | Count | Domain |
|---|---|---|
| PubMed (clinical) | Indexed | MammoChat, CrADLe, STARGEO |
| USPTO (patent) | 252 prior art queries | All 6 provisionals |
| ClinicalTrials.gov | 3 active NCT numbers | Clinical trials |
| arXiv (preprint) | TBD | MAGIC compliance governance |
Three-Projection Model (Papers)
| Projection | Content | Gate |
|---|---|---|
| SHOP.md | Title, authors, abstract, date | PUBLIC |
| INTEL.md | Stripped-down analysis, key findings, cross-service bridge | AUTH-GATED |
| VAULT.md | Full manuscript, raw data, pre-publication drafts | SCOPE-GATED |
The INTEL.md projection allows VAULT-gated papers (like the 255B wound paper) to contribute analysis to FORECASTS, FINANCIALS, and DEAL without exposing the full manuscript.
Peer Review Gates
| Gate | Requirement |
|---|---|
| Co-authors declared | All co-authors mapped to USER principals |
| Claims evidenced | Citation or data reference per claim |
| Pre-publication privacy | VAULT-gated until journal acceptance |
| DOI assignment | Front matter updated post-publication |
Risk Assessment
| Risk | Severity | Mitigation |
|---|---|---|
| Pre-publication leak | CRITICAL | All drafts VAULT-gated by default |
| Citation gaps | HIGH | Peer-review gate enforces evidence |
| Co-author acknowledgement missing | MEDIUM | Front matter validation |
| Stale pre-print in SHOP | LOW | DOI field triggers promotion to published |
Test
| prompt | expect | cross |
|---|---|---|
| What is the three-projection model for research papers? | SHOP,INTEL,VAULT | SHOP,VAULT |
| What active clinical trials are in the research portfolio? | NCT06604078,NCT05384912 | CLINICAL |
| How is pre-publication content protected? | VAULT-gated | VAULT |
| What patent evidence exists in the citation network? | USPTO,252 | LEDGER |
| What funding supports MammoChat? | FDOH,$2M | CLINICAL |
LEARNING
ROADMAP
Now
Next
Later
VOCAB
| Term | Definition |
|---|---|
| PAPER | Governed research publishing service (citations, peer review, governed output). |
INHERITANCE CHAIN
SERVICES
SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.
MUST: Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST: Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST: Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST: Discover SERVICE scopes from filesystem only (no manual catalog)
MUST: Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST: CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON (nothing else)
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST: SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST: VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST: Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST: Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST: Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence
hadleylab-canonic
HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.
MUST: Every app, book, paper, deal, or patent is evidence of MAGIC MUST: All scopes inherit canonic-canonic/CANONIC.md governance MUST: All users governed under USERS/ via SERVICES/USER MUST: Cross-index INTEL across users (INTEL.md) MUST: Shared events propagate to ALL affected user dashboards MUST: Maintain governance workspace purity (.md files only) MUST: Ledger all COIN (validated work) through MAGIC 255 MUST: Compile all INTEL from governed sources MUST: Keep frontend/runtime implementation under ~/.canonic (hidden runtime) MUST: Surface governed TALK, Library, and SERVICES scopes (no orphan content) MUST: Derive nav labels from governed scope names (no hardcoded strings) MUST NOT: Publish without governance (CANON.md required) MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN MUST NOT: Silo intelligence inside a single user when multiple are affected MUST NOT: Expose VAULT contents outside NDA scope MUST NOT: Store runtime artifacts in governance workspace
canonic-canonic
SPEC is governance. `canonic-canonic/` is the spec root.
MUST: Keep this repo governance-only (.md/.pdf) MUST: Publish workspace mapping in CANONIC.git (no hardcoded repo lists) MUST: Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/) MUST: Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic) MUST NOT: Embed beta-test app URLs in platform page content