The data room.

Tier 1 is issued automatically on a soft gate: name and email, with a short disclaimer acknowledging the material is forward-looking. Access persists thirty days via a signed cookie. Revoke at any time by emailing invest@tekku.app.

Tier 2 requires two steps. First, a Clerk account with role investor or admin, provisioned by Tekku. Second, a short NDA countersigned and returned. The PIN is issued over the same channel the NDA was returned on (usually email). PIN access persists until revoked, with a mandatory re-verify prompt every ninety days.

Admin role sees all folders regardless of tier. Investor role sees Tier 1 openly and Tier 2 behind the PIN. Anonymous visitors see only the marketing summary above and the folder labels; they do not see counts, document titles, or last-updated timestamps.

Add. New documents land in the Supabase storage bucket, a row is written to crm.documents with folder, tier, and uploader metadata, and the upload shows in the recent-uploads list on the landing page within a request cycle.

Redact. If a document needs to be redacted after publication, the redacted copy is uploaded as a new file, the original is archived (not deleted), and the row is superseded with a reference to the archived predecessor. The lineage remains visible to admin.

Supersede. When a document is replaced (a new scenario output, a revised counsel memo), the prior version is archived in place and the new version takes its slot. Every supersede event writes an audit row and updates the folder last-updated timestamp.

Archive. Archived documents are not deleted. They remain accessible to admin for compliance and are never purged except on an explicit legal-hold release.

If an allocator asks for a document that is not yet published, the request routes to invest@tekku.app. We triage within one business day. The response is one of three shapes. One, the document exists and we publish it to the correct folder within one to three business days. Two, the document does not yet exist and we produce it, estimate a date, and commit. Three, the document exists but we are not ready to publish it externally, in which case we explain why and offer an alternative artifact that answers the underlying question.

Requests are treated as signal. If three different allocators ask for the same missing artifact, it moves to the front of the queue without further prompting. The request log itself is a Tier 2 document under the process folder.