@holoscript/papers-program

Consumer-facing package for the HoloScript papers process.

The package does not ship private drafts, PDFs, or submission material. Point it at a triad config and paper matrix shards, and it emits the process a consumer or external agent should follow before treating a paper claim as product-backed.

npm i @holoscript/papers-program
papers-program report \
  --triad config/competitor-paper-codebase-triad.json \
  --json

Program rules:

• papers are product claims, not detached prose
• every paper claim should route to code evidence or an explicit blocker
• competitor responses need the competitor-paper-codebase triad before promotion
• editor contact, ordinary paper submission/release, and public claims made by an agent or the project are agent-decided
• Joseph review is limited to the exact four protected classes: spend beyond an active per-rail cap or changes involving the treasury master wallet, Trezor seed/recovery, new-wallet creation, custody or minting authority, or permanent seat-wallet identity; a physical commitment requiring his body/signature/presence; a public commitment under his name/face/voice; or a governance-tier mutation. Within-cap existing-wallet sign/broadcast is agent-decided.
• in the papers lane, the identity trigger is specifically a byline, submission, or public commitment that uses Joseph/the founder's name, face, or voice
• legal, export-control, and compliance questions route to qualified specialist review; that review is separate from Joseph approval
• research outputs close with receipts and validation evidence

API:

import { buildPapersProgramReport } from '@holoscript/papers-program';

const report = buildPapersProgramReport({ triadConfig, paperRows });

Consumption Contract

External users, founder reviewers, and agent operators bring their own caller-provided triad config, paper rows, source citations, storage, credentials, and publication process. This package does not ship founder-local drafts, private submission state, GOLD intake, byline authority, or local hardware assumptions. It emits a report/process primitive; callers own promotion, rollback, and receipt storage.

Agent-operable evidence: run papers-program report --json and attach the JSON output or downstream validation receipt before treating a paper claim as product-backed.

Release boundary: v0-preview. This report-only preview does not itself submit papers or contact editors; that is a feature boundary, not an approval gate. Caller-owned agents may perform those actions under the authority contract above. The package does not use Joseph's identity without review or replace the competitor-paper-codebase triad.