← Red Eagle project hub

The draft storyboard is behind a members gate.

Access is by request. It takes about a minute, and it is recorded.

It’s a working draft file that requires consultation with Muscogee tribes when ready. This gateway is designed to maintain some level of control over where this project ends up getting published.

Request access

What is recorded: your email address, when access was granted, and which pages and panels you open. Views are kept for 24 months; the record that access was granted is kept for the life of the project. Ask and it is deleted.

What your access is for

Membership is not a viewing pass. Members are asked for notes — on accuracy, on wording, on what a panel gets wrong — and every note follows the route below. Nothing you write is edited away or quietly dropped: a note lands on the source file beneath the panel, the panel is rebuilt, and the parts of the route that do not exist yet are drawn as gaps rather than hidden.

Feedback action map

What happens to a reader’s note

one-way flow · edit the source, rebuild the output · 10 note categories · 3 reserved

The new hash is cache invalidation: earlier notes are re-checked, never assumed.

The website Built

1A member writes a note

Input capture: the note keeps two pointers, the frame it is about and the exact panel build the member saw.

Captured

2The site triages, the author rules

A daily job proposes accept, decline, or ask, but the machine only advises. Reserved questions skip it and reach the author.

Proposal and ruling live in separate columns: never overwrite your inputs.

Unread → one open port: the author pulls, append only

The boundary, one way Built

One port, one direction

Think firewall with one port: the website cannot reach the project; the author’s machine pulls accepted notes across, and nothing else crosses in either direction.

The project Proposed routing drafted, not yet ruled

3Reserved questions

Accuracy, sequence of events, depiction of people. Questions of fact get a human ruling.

Ends in a ruling, not an edit

3Wording & staging

Captions, staging, composition, pacing. Edits to source files, never to a finished panel.

Patch the source, not the output

3Image faults

First isolate the layer: a bad render is a project problem, a broken page is a site problem.

Re-render

3No home yet

Alt text has no file to land on yet, a real gap, drawn as one. “Something else” is re-sorted first.

No landing yet

Where a note lands, four tiers

SourcesWhat happened, and how we know.
InterpretationWho was where, in what state.
The pageThe writing.
The renderCompiled output, never hand-edited.

Layered design: each tier is derived from the one above it. Edit as high as the note requires, then rebuild everything beneath. Accepted is not applied.

The rebuild Built

  • An edit landsEdit the single source of truth.
  • 4RebuildsDerived artifacts are regenerated, never patched.
  • 5PublishesPublished: a new panel hash.

The “applied” record Not built

No provenance log: accepted and applied are different states that currently look identical.

Fig. A reader’s note never edits the panel it points at. It crosses a one-way boundary, lands on the source file beneath that panel, and the panel is rebuilt from there. That is the rule of any good build system: fix the source, regenerate the output, and let the new hash tell you what to re-check. Three kinds of note are reserved for a human ruling, one kind has nowhere to land yet, and the record that a note was applied does not exist yet. The diagram draws those gaps instead of hiding them.

What is behind it

The screenplay of record broken into 221 beats and laid against the panels that exist. 44 are drawn. Twelve are withheld outright because the page depicts a killing. The rest are clear and not yet generated — and the page says so beat by beat rather than showing only the finished ones.

It adapts peer-reviewed research on William Weatherford and the end of the Creek frontier, published in 2012. That matters here: this is controlled work from a verified source, not a hobby project’s sketches, and the gate exists because a draft depiction drawn from attributable scholarship should not circulate out of context.

How the gate works

  1. You submit an address. A single-use link is generated and emailed to it.
  2. Opening the link verifies the address is real and starts a seven-day session. The link then stops working — a second use is refused and flagged.
  3. The storyboard and every panel are held in private storage with no public URL. Nothing is served from the site’s public files.
  4. Each page and each panel is fetched through a check against your session, and each fetch is written to an append-only log.

The point is not to build a wall. Anyone who asks gets in. The point is that every byte that leaves is attributable to someone, and that the question who has seen this draft is answered from a record rather than from memory — because that is a question the consultation will fairly ask.

What it is built on

Aaron Zeanah · Red Eagle project hub · Portfolio
Published: “The End of the Alabama Frontier: Weatherford’s Perspective,” International Journal of Interdisciplinary Social Sciences, Vol. 6, No. 4 (2012).