# OURS TODAY · Day 1

**Date:** 26 August 2026  
**Machine date:** `2026-08-26`  
**Status:** LOCAL BUILD RECORD · PUBLICATION PENDING  
**Edition:** DAY 1  
**Theme:** The network forming itself in public

Day 1 begins when the founding thesis becomes precise:

> # THE NETWORK IS OURS. EVERYTHING ELSE CAN BE BUILT.

> **OURS is a member-owned network that builds its own software in public.**

The prior Mission Market work is prehistory. It is preserved because it
contains useful mission, cell, migration, economics and governance thinking.
It is not presented as a public failure and does not consume Day 1.

---

## 1. What Day 1 decides

### Adopted

- The institution is **OURS**.
- The daily public product is **OURS TODAY**.
- The canonical intended domain is `ourstoday.com`.
- Day 1 is 26 August 2026.
- The first product is the network forming itself in public.
- A verified entrant receives a chronological, non-tradable Founding Ledger
  place when entry is sealed.
- There is no 15-minute reservation.
- A successor activates a connection, not the predecessor's belonging.
- A click, reaction or impression has no canonical authority.
- External networks distribute proposals; OURS keeps canonical memory and
  authority.
- Agents draft and build. Stewards decide operations. Members will ratify
  constitutional questions after legal membership exists.
- No token, tradable credit, referral votes or fictional social proof.
- The Mission Market returns only when real cells exist.

### Constitutional status

The project adopts [Founding Constitution 0.1](./CONSTITUTION-0.1.md) as its
operative charter.

It has not been legally ratified by members because legal membership has not
been issued. Every public surface must say so.

---

## 2. What shipped in this repository

### Day 1 homepage

The Day 1 homepage replaces the fictional multi-cell market with:

- the founding declaration;
- current ownership/legal status;
- Founding Ledger origin row `000001 · RADO`;
- the rule that a successor activates an edge, not a person;
- a local entry-draft interaction that cannot claim a canonical number;
- Formation Tape;
- Build Tape;
- Constitution Diff;
- the first open case;
- links to every source document.

### Source package

- [OURS founding direction v0.2](./OURS.md)
- [Founding Constitution 0.1](./CONSTITUTION-0.1.md)
- [Founding Relay Protocol](./FOUNDING-RELAY-PROTOCOL.md)
- [Proposal and Deliberation Protocol](./PROPOSAL-AND-DELIBERATION-PROTOCOL.md)
- [Agent Build Contract](./AGENT-BUILD-CONTRACT.md)
- [Founding Ledger backend build handoff](./FOUNDING-LEDGER-BUILD-HANDOFF.md)
- [Next coding session prompt](./FOUNDING-LEDGER-NEXT-SESSION-PROMPT.md)
- this Day 1 record

### Preserved prehistory

- [OURS founding direction v0.1](./OURS-v0.1.md)
- [Mission Market design proposal](./mission-market.html)
- `archive/mission-market-v0.1/` — the prior multi-file homepage

---

## 3. Implementation truth

### Shipped locally

- dependency-free HTML, CSS and JavaScript;
- responsive founding-instrument layout;
- semantic navigation and controls;
- local entry-draft state;
- local copy/export behavior where explicitly labeled;
- public source documents;
- reversible archive of the previous interface.

### Not shipped

- production hosting or deployment;
- registered/connected `ourstoday.com`;
- shared database;
- identity verification;
- canonical number allocation;
- signed relay tokens;
- cross-person continuation;
- production proposal ingestion;
- legal entity or membership issuance;
- member voting;
- production privacy, security, support and incident operations.

Therefore:

> **No action on the local homepage creates a canonical Founding Ledger entry,
> legal membership or ownership.**

The interface must preserve this sentence until production gates pass.

---

## 4. Founding record

The Day 1 visual instrument displays:

```text
000001 · RADO
ENTERED: 26 AUG 2026
ARRIVED THROUGH: ORIGIN
RELAY: OPEN
LEGAL MEMBERSHIP: NOT YET ISSUED
```

This is the declared origin of the formation story. The production ledger must
either import it through a reviewed genesis event or explicitly identify it as
a founding declaration outside the later allocator. That implementation choice
requires a decision receipt before production launch.

No additional public person or count may be invented to make the network appear
larger.

---

## 5. The intended live entry ritual

When production gates pass, the visitor flow becomes:

1. Read the declaration and current legal status.
2. Choose a public display name or approved pseudonym.
3. Verify through the adopted identity path.
4. Accept the declaration and consent record.
5. Canonical transaction assigns and seals the next ordinal.
6. Receive a stable entry page and signed relay.
7. Decide whether to post, copy or send it.
8. A later verified successor creates the continuation edge.
9. Return to perform a real test, commitment or stewardship act.

No step reserves an ordinal. No platform account is required for the right to
enter.

---

## 6. Founding share language

### Entry

```text
I entered the Founding Ledger of OURS as #000002.

The network is ours. Everything else can be built.

Continue the line from me: https://ourstoday.com/r/<token>
```

### First Continuation

```text
The line continued.

#000019 entered OURS through #000002.
```

### Proposal

```text
OURS is deciding P-0001 in public:

Should the Founding Era close when Constitution 1.0 is ratified?

Add evidence, commit to test, or object with a reason:
https://ourstoday.com/p/0001
```

Generated language remains editable. OURS does not silently publish on a
person's behalf.

---

## 7. The first open case

### P-0001 — When does the Founding Era end?

**Class:** Constitutional signal  
**Current status:** GATHERING EVIDENCE · NOT OPEN FOR RATIFICATION  
**Proposed answer:** when Constitution 1.0 receives valid founding-member
ratification, not when an arbitrary number of people enter

#### Case for

- It ties founder status to an institutional achievement rather than artificial
  scarcity.
- A viral burst does not arbitrarily exclude people because a counter filled.
- Low chronological numbers already preserve early courage.
- The founding cohort has a defined job: constitute the institution.

#### Case against

- Ratification timing may be delayed by legal work.
- An undefined period can make “founding” feel indefinite.
- People entering under different constitutional drafts may have different
  expectations.

#### Evidence needed

- legal feasibility of pre-membership/founding eligibility;
- understandable disclosure for entrants;
- expected time to Constitution 1.0;
- whether the term materially changes propagation or trust;
- a fair transition if legal issuance is delayed.

#### Authority

Founder-steward may open the case and commission legal review. It cannot be
labeled member-ratified before legal members and a valid ratification process
exist.

---

## 8. Day 1 causal tapes

### Formation Tape

| Event | State | Truth |
|---|---|---|
| Founding declaration adopted | RECORDED | Founder-steward project decision |
| Origin row designed | FRONTEND | Not yet a production database event |
| Production ledger opened | NOT SHIPPED | Blocked on production gates |

### Build Tape

| Input | Decision | Build | Test | Result |
|---|---|---|---|---|
| “The network is the only power incumbents cannot beat if it is ours.” | Formation becomes the first product. | Replace Mission Market homepage with Day 1 instrument. | Local structural, link, syntax and static-accessibility checks. | Recorded in the repository build receipt/handoff. |
| “A 15-minute reservation will fail in a viral loop.” | Assign only at verified commit; successor activates edge. | Write relay state and concurrency protocol. | Protocol review and future concurrency tests. | Specification shipped; backend not built. |
| “Discussion can create more reach on X and LinkedIn.” | Outsource reach, not memory or authority. | Write canonical proposal protocol. | Future proposal pilot. | Specification shipped; ingestion not built. |

### Constitution Diff

```diff
- The first public product is a Mission Market of cells.
+ The first public product is the network forming itself in public.

- Everything can be built. What should become ours?
+ THE NETWORK IS OURS. EVERYTHING ELSE CAN BE BUILT.

- Public momentum leads the first experience.
+ Chronology, causal participation, current legal truth and public building lead.

+ Ledger entry cannot depend on audience or successor.
+ External platforms distribute; OURS retains canonical memory and authority.
```

The full superseded direction remains in [OURS v0.1](./OURS-v0.1.md).

---

## 9. Day 1 success and failure evidence

The Day 1 page is not validated merely because it looks original.

### First product questions

- Can a visitor accurately repeat the thesis after one view?
- Do they understand that legal membership is not yet issued?
- Does entry feel honorable without artificial scarcity?
- Do people understand that the first successor activates the edge?
- Do they want to return for the next build or decision?

### Production relay measures

Once live:

- verified entry completion rate;
- verification abandonment by step;
- percent who intentionally create a share/copy action;
- percent with a verified First Continuation;
- time to First Continuation;
- percent returning for a real act;
- suspected duplicate and void rate;
- withdrawal and support rate;
- accessibility and incident reports.

Views, impressions and follower totals remain context, not proof.

### Stop conditions

Pause canonical entry if:

- duplicate/bot entry exceeds review capacity;
- number allocation or idempotency is uncertain;
- private data appears in a public projection;
- withdrawal or export fails;
- legal/status language is misleading;
- incident response lacks a named human;
- viral load threatens data integrity.

The page may remain readable while entry is paused.

---

## 10. Next build

The next coherent product slice is production-readiness design, not another
visual concept:

The executable architecture, staged work, production gates and ready-to-copy
agent prompt are now defined in the
[Founding Ledger backend build handoff](./FOUNDING-LEDGER-BUILD-HANDOFF.md).

1. implement the locked Next.js and provider-neutral PostgreSQL architecture;
2. obtain privacy/legal review for entry fields and status language;
3. implement entry draft, verification, seal and idempotency;
4. implement signed relay and atomic First Continuation;
5. implement withdrawal, export, backup and recovery;
6. run the relay acceptance matrix;
7. publish a founder-steward readiness receipt;
8. only then open the canonical Founding Ledger.

Proposal P-0001 and the first production Change Pack can be built after the
shared ledger foundation is safe.

---

## Day 1 closing line

There are not yet millions of people here. There is no invented market and no
false social proof.

There is one origin, an explicit constitution, a protocol for the next
connection and a public record of what is true.

> **THE NETWORK IS OURS. EVERYTHING ELSE CAN BE BUILT.**