Packet setup

Paper setup

Lock the governing claim, domain, pressure, owner, and the sources and passages in section order. Henry can help name the claim. It cannot invent sources.

Paper OS project

Choose the workflow that governs the paper

SCRIPTO keeps the project control, node handoffs, and author gates in this browser. The packet workflow below remains a separate evidence review.

Project not configured

Select an operating system HSS Paper OS One article. Sixteen sequential nodes, source discipline, and submission checks. Paper Series OS One series paper. Seventeen nodes, deconstruction, author gates, and series continuity.

Working title required

Author required

Target journal

The author retains every substantive decision. SCRIPTO can record a gate decision, but it cannot infer or approve one.

Node 00

Intake and Corpus Formation

Configure a project to begin the governed node sequence.

End this node with a handoff

8 fields required to close

Record what actually happened. A handoff makes the next session reconstructible. It does not assert that any source, claim, or paper is verified.

Paper title

Use the real paper title or the working argument.

Accountable owner required

The Control Registrar binds this name to a finding. Do not invent a person.

Outline file TXT, MD, DOCX

No outline loaded yet. Upload a .txt, .md, or .docx outline. Older .doc files should be resaved as .docx first.

Governing claim required

The single sentence this packet remains accountable to.

Consequence domain required

This frames the risk surface and the level of precision the packet must satisfy.

Recursive pressure required

Pressure level decides how aggressively the packet should challenge its own wording.

Sources and passages required Section order

Add sources and passages in section order: Literature review, Background and Context, Theories and Concepts, Analysis, Findings, Discussion, Conclusion.

Keep only sources and passages you actually have. Henry will not invent a literature.

Step 2

Map the claims

Keep the paper's governing claims in three lanes: direct evidence, supported inference, unresolved unknowns.

Support lanes stay explicit

Method rule: if a claim outruns its visible source anchor, narrow it or mark it as unresolved. Do not let fluent wording impersonate evidence.

Accuracy boundary: seeded claims are heuristic candidates based on visible lexical cues. Confirm the text, class, and anchor note manually before letting any seeded line travel.

0 claims mapped

0 direct 0 inferred 0 unresolved

No claims yet. Seed candidates from the manuscript, then keep or drop each line.

Step 3

Mark the checks you ran

Tick only what you actually did. Low or medium pressure needs one check or a contradiction note. High or critical pressure needs the pre-pass, overclaim, and unresolved-unknown checks (c3, c5, and c6).

Fail-closed pressure

Progress 0 / 6 passed

Contradiction notes

Step 4

Run the three Henry reviews

Supportive, cold-method, and harsh. All three must come from a Cloudflare Worker on this manuscript. Local heuristic notes do not count. Invented citations are flagged.

AI-assisted scholarly pressure

Henry is waiting for a Worker call.

This is the main action on this step. One click sends the frozen packet to the Cloudflare Worker.

Supportive focus

Confirms what the manuscript already anchors well and where the argument is behaving responsibly.

Awaiting review trigger.

Cold-method focus

Evaluates inference drift, missing source classes, and unearned causality without praise language.

Awaiting review trigger.

Harsh focus

Names the single sentence most likely to fail under cross-examination and explains why.

Awaiting review trigger.

Step 5

Name who owns the next review

One complete row: owner, finding, evidence, and interval. Without it the packet is not ready.

Controls bind to interfaces

Gate: export should not travel without at least one complete control row. If nobody owns the next review, the packet is not ready.

Step 6

Export the paper packet

Download one markdown file with the governing claim, reviews, disclosure, and the named owner of the next revision.

Markdown packet ready

Readiness Not ready

Words 0

Mapped claims 0

Complete controls 0

Markdown export

Ready for bounded export

1 of 6 · toward claims