Initialize Labyricorn site source

2026-07-23 11:10:39 -07:00
commit b918b70fe4
9 changed files with 272 additions and 0 deletions
@@ -0,0 +1,31 @@
+# Authoring Content
+
+Content is written in Markdown and committed to Git.
+
+## Front matter
+
+Every document begins with YAML front matter. At minimum, provide:
+
+```yaml
+---
+model: article
+title: Example title
+slug: example-title
+status: draft
+---
+```
+
+The `model` value must match an installed and enabled Labyricorn content-model
+definition. Model behavior comes from configuration; the engine must not
+special-case the model name.
+
+## Publishing state
+
+Use `status: draft` while working. Change it to `status: published` when the
+document is ready for the public site.
+
+## Media
+
+Place intentionally public assets in `media/`. Do not commit credentials,
+private source files, local configuration overrides, or generated site output.
+
@@ -0,0 +1,51 @@
+# Initial Deployment
+
+This document defines the first deployment boundary. It does not assume GitHub,
+Cloudflare Pages, Docker, or a public Control Plane.
+
+## Target environment
+
+- Gitea: `https://git.labyricorn.com`
+- Labyricorn: installed directly in an LXC container
+- Control Plane: private network access only
+- Public site: static output served by the configured local runtime
+- Canonical site address: `https://labyricorn.com`
+
+## Deployment sequence
+
+1. Create an empty repository on `git.labyricorn.com`.
+2. Add that Gitea repository as the remote for this local repository.
+3. Push the default branch to Gitea.
+4. Connect the repository in the Labyricorn Control Plane.
+5. Synchronize it and confirm `.labyricorn/site.yml` is valid.
+6. Confirm that the `page`, `article`, and `project` models are installed and
+   enabled in Labyricorn.
+7. Confirm discovery finds the three Markdown documents in this repository.
+8. Preview the generated routes and resolve any validation errors.
+9. Build the site.
+10. Publish the completed build to the local canonical site.
+11. Verify the homepage, article, and project page from a browser.
+12. Record the deployed Git revision and active local release.
+
+## Required proof
+
+The initial deployment is successful only when all of the following are true:
+
+- the repository revision shown by Labyricorn matches Gitea;
+- configuration validation uses the committed `site.yml`;
+- all three source documents are discovered without filename heuristics;
+- generated routes come from configured model behavior;
+- the public pages are served from the activated local release;
+- restarting the Control Plane does not erase deployment state;
+- no operational success status is fabricated.
+
+## Not part of the first deployment
+
+Add these only after the local path is proven:
+
+- GitHub deployment mirror;
+- Cloudflare Pages;
+- anonymous comments;
+- social sharing automation;
+- additional projections or publishing targets.
+