The plan follows the one of the Go reference: the codec first, then the
reader together with the testdata of spec-v0.10 in one commit, as the
v0.9 did, since the guard of the harness wants every synced file read by
a test; then the writer, the ZIP of the page and the two pages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
At the author's request, main fast-forwarded from 7e2d83c (spec-v0.9)
to cc35d2c (spec-v0.10), without a merge, and is on the remote.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The author authorized the push and the tag. The branch v0.10 of
datekeys-go and the annotated tag spec-v0.10 are on the remote at
cc35d2c; main stays at v0.9.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
datekeys-go branch v0.10, unpushed, holds the nine steps of the plan,
from 631d09c to 6fa2b54, and a fix of the CLI, 735885c. scripts/check.sh
60s is clean. The handoff records what was done, the checks, what the
author has to decide (the push and the tag spec-v0.10, an editorial
change in section 67 of the approved text, the size of the mutation
corpus) and what datekeys-ts starts with. The plan marks each step with
its commit.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nine steps on the datekeys-go branch v0.10, from the Unicode tables to
the spec-v0.10 tag; step 0, the data, is done.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
R4b and the text rule keep invisible sequences out of paths, comments
and the declared author, after the warning of Unicode 18.0.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The author chose Unicode 18.0.0 and approved the draft. The handoff
lists what implementation still needs from the author: a proposal to
close the invisible-character channel that Unicode 18 warns about, and
permission to download the Unicode and WindowsBestFit data files.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- spec_v0.10/revision_borrador.md records the final review of the
draft (datekeys-go branch v0.10): one blocking, three major and
eleven minor corrections, all applied there in 9d1cd2e.
- The design follows the corrections that touch it (annex D): R6c only
rejects '/', '\', ':' and U+0000 in a best-fit projection, so "¿"
and "♥" are accepted; the CLI prefixes paths too, redirected or not.
It also answers the author's question on several signatures: a
future alg can carry a list without changing the format.
- The handoff records the state and the next steps: the author picks
the Unicode version of the tables (18.0.0 came out on 16-09-2026)
and approves the text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The author closed them on 30-09, all with the recommendation. The limits
stay as proposed and freeze with format 3. A single file inside a folder
downloads directly, with the ZIP as a second option, and the page offers
each file of the ZIP as an uncopied slice of it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Records what the session of 30-09 at midday did to the format 3 design,
the interpretation of the third decision that the author has to
confirm, and the next step: the author closes the ten open questions of
delivery 1 before the spec v0.10 text is drafted. Also brings the
repository table up to date for datekeys-ts and notes that the pending
steps of the reorganisation are still open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
formato3_diseno.md is now the single source of the format 3 design. The
two files that repeated its text are gone; the package Fable reviewed
stays in git at 56851a9 and in the published artifact.
- Part 0 gives outside readers the v0.9 protocol, a glossary, the
author's decisions and the threat model with its accepted leaks.
- Parts 1 to 3 are the deliveries. Delivery 1 freezes the format: a
12-byte content framing with AREA_LEN, a security map that stays at
version 1 with its signature and seal carried as separately encoded
byte strings, the head, the path rules R1 to R10 and the verdicts.
Delivery 2 adds the Ed25519 author signature; delivery 3 the seal on
seal.datekeys.com, with its proof inside the capsule, an offline root
and proof of work.
- Fable's findings 2 and 5 to 10 and the notes on the document are
applied; annex A says where each finding is resolved.
- Annex B folds the internal review into 24 objections, each marked
corrected or accepted.
- An adversarial review of this version found nothing blocking or
major; its 15 minor findings and the six follow-ups of a second pass
are applied and listed in annex C.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 6 records the page decisions of the author, step 7 the page and
its adversarial review. The handoff resumes at the author's decision on
closing 0.2.0.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The plan table records each step with its commit; the handoff resumes at
step 6 of the plan, the page decisions, which the author confirms, and
drops the stale 0.1.0 question.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replans the writer on the writer rules of spec §62.1: format 2 only,
L known before sealing, reforzado padding by default, 16 slots with
dummies in a uniform order, recipients checked as Go does,
SEALED_CONTROL_LEN from the §62.1 formula with the real seal checked,
and the self-checks of rule 11. An adversarial review found no blocker
and no major issue; its 12 minor corrections are incorporated. The 17
decisions await the author's confirmation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
datekeys-go 4a025d1 applies all 22 corrections of the final review of the
v0.9 draft, plus four places that repeated them. The author decided
correction 2 on 29-09: the section 56 rule is softened, so the streaming
readers of Go and TypeScript stay valid. Correction 10 drafts open question
4 as a MAY. Step 1 of the work order is done; next is the author's approval
of the text.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new section 0 records the reorganization of 29-09 and what is left for
the author: renaming App to datekeys-ts once no session holds it open,
opening sessions at the workspace root, deleting the duplicate
enquiry.php, and giving docs and web a remote if wanted.
Section 2.5 now says what was checked: the final review of the v0.9 draft
has 22 entries, not 21, and none is applied in 1189f2f, so all are
pending. It points to spec_v0.9/review.md and names the entry that needs
the author's decision (the section 56 MUST NOT).
The repository table follows the new folder names, and the rules and the
document list now point to the README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The handoff, the plans and the protocol review come unchanged from
go/DateKeys-App at f660f0c, where they lived in docs/. They describe the
whole project, not the TypeScript implementation, and they are internal,
so they get their own private repository.
spec_v0.9/ holds the working papers of the v0.9 draft (datekeys-go 1189f2f):
the design note, the two design reviews, the drafting report and the final
review with its 22 pending corrections. They were only in a temporary
session folder.
The README maps the workspace and carries the project rules, which the
handoff used to hold in its section 3.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dev