generated from Labyricorn/labyricorn-project-template

Files

T

Labyricorn 835d966e75 Revert "docs(devlog): add missing devlog entries for Steps 5, 6.3, and Step 6 completion"

This reverts commit 7249b33fca.

Removes the four devlog entry records added by that commit
(step-5-completion, step-6-surface-discovery,
contract-5-3-accepted-baseline, step-6-completion) and restores
.labyricorn/devlog/contents.lr to its prior title and summary.

The annotated tags contract-5.3-accepted-baseline and step-6-complete,
and all underlying implementation, documentation and evidence, are
unchanged. Only .labyricorn/devlog/ publishing records are affected;
the uncommitted project identity record and other working-tree changes
are deliberately left out of this commit.

python devlog_editor.py --validate passes; git diff --check clean.

2026-09-17 17:53:38 -07:00

devlog

Revert "docs(devlog): add missing devlog entries for Steps 5, 6.3, and Step 6 completion"

2026-09-17 17:53:38 -07:00

project

Initial commit

2026-09-13 20:52:53 -07:00

AGENTS.md

Initial commit

2026-09-13 20:52:53 -07:00

README.md

Initial commit

2026-09-13 20:52:53 -07:00

README.md

Labyricorn publishing content

This directory is the repository-owned source for this project's exhibition and development log on Labyricorn. The project repository remains the source of truth; the Labyricorn site imports this content as read-only.

The content uses native Lektor records:

.labyricorn/
├── AGENTS.md
├── README.md
├── project/
│   ├── AGENTS.md
│   ├── contents.lr
│   └── <optional image>
└── devlog/
    ├── AGENTS.md
    ├── contents.lr
    └── <entry-slug>/
        ├── contents.lr
        └── <optional images>

Rules:

project/contents.lr uses the project model.
devlog/contents.lr uses the devlog model.
Each entry is a directory below devlog/ containing a contents.lr record using the devlog-entry model.
Entry directory names are stable public slugs. Do not rename a published entry without arranging a redirect on the Labyricorn site.
Dates use YYYY-MM-DD; source_commit uses the full relevant commit ID.
Publishing attachments stay inside the record subtree that owns them.
Do not put credentials, builds, application state, or executable code here.

Editing these records does not itself prove that the public site synchronized. Report repository publication and Labyricorn synchronization separately.