Document Intake Covenant

This is a public orientation page for how new material enters the project. It is not an essay, a raw source, or a canonical chapter.

The covenant exists to keep the archive from growing by mere accumulation. New documents should serve faithful discernment, public clarity, and the path of return into Christ.

Governing Rule

Raw material is preserved carefully, but preservation is not publication. Publication is not canonization. Canonical development is not automatic authority.

Every intake decision should protect these distinctions:

  • raw/ preserves source material, drafts, PDFs, notes, and held documents.
  • markdown/ contains public reading copies of essays and related works.
  • root .qmd pages orient readers through the public site.
  • architecture-of-apostasy/ develops canonical theological grammar and project structure.
  • gallery/ contains public visual assets.
  • ai-system/ contains servant tools, schemas, prompts, checks, and implementation support.

The archive must remain a servant of faithful keeping, not a monument to its own growth.

Intake Flow

Every new document should pass through a deliberate process before it becomes public, canonical, or held in reserve.

Raw source received
  ->
Preserve faithfully in raw/
  ->
Extract or convert to markdown/ when appropriate
  ->
Classify the document
  ->
Map it to canonical terms
  ->
Identify source needs and rival readings
  ->
Run mechanical checks
  ->
Human editorial review
  ->
Publish, revise, canonize, or hold in reserve

Staging Folder

The operational landing zone for new batches is intake/.

Users may place PDFs, Markdown drafts, images, source notes, or mixed batches in that folder and then ask Codex to run the intake process. The folder is not a permanent home. Intake should inventory the batch, read or inspect every item, classify the material, check theological fit, move accepted files into their proper locations, update the website pages that expose them, validate the site, and then remove the ingested files from intake/ while leaving intake/README.md in place.

If a file cannot be placed safely, it should remain in intake/ with a clear explanation. Ambiguity is not failure; it is a signal that human editorial judgment is needed.

Classification

The first intake question is simple: what kind of document is this?

Possible classifications include:

  • Essay
  • Mythic or devotional work
  • Song
  • Image or image note
  • Discussion
  • Source note
  • Prompt
  • Canonical chapter
  • Raw archive item

Classification protects the reader. A mythic work should not be treated as technical ontology. A raw draft should not be treated as finished public argument. A prompt should not be treated as theological authority.

Intake Questions

Before a document moves forward, it should answer these questions:

  1. What kind of document is this?
  2. What created good is being examined?
  3. What corruption, false logos, or fallen liturgy is being exposed?
  4. What cry is being heard?
  5. What wound does this document carry?
  6. What claim types are present?
  7. What evidence is needed?
  8. What rival reading should be considered?
  9. Where does it belong in the repository?
  10. Does it clarify the path of return, or merely enlarge the archive?
  11. Does it resolve in Christ, or only diagnose collapse?
  12. If this is an essay with a companion image, has the image been placed near the top of the public Markdown copy and listed in the gallery?

These questions should slow the project down when speed would confuse raw intensity with faithful increase.

Possible Outcomes

After review, a document may be:

  • preserved only in raw/;
  • converted into a public reading copy in markdown/;
  • used to improve a root orientation page;
  • mapped into canonical work under architecture-of-apostasy/;
  • routed into gallery/, songs.qmd, or discussions.qmd;
  • paired with a companion image near the top of its public Markdown copy when the relationship is clear;
  • sent back for sourcing, claim classification, rival readings, or pastoral review;
  • held in reserve;
  • declined for publication.

Holding a document back is not failure. Sometimes faithful keeping means refusing to turn every source, wound, warning, or image into public material.

Review Standards

Public work should have a clear purpose, belong in the right repository layer, identify its claim type or genre, and avoid confusing raw material with canonical theological development.

It should clarify the path rather than merely expand the site. It should preserve humility where evidence is incomplete, resist contempt, and gesture toward Christ, restoration, repentance, or faithful keeping.

Canonical work carries a higher burden. It should use canonical terms consistently, distinguish doctrine from synthesis, cite sources proportionate to its claims, include objections or cautions, and resolve in Christ.

Status Labels

When tracking new materials, these labels can describe the current intake state:

  • raw-preserved
  • markdown-converted
  • needs-summary
  • needs-citations
  • needs-claim-classification
  • needs-rival-readings
  • needs-pastoral-review
  • ready-for-public-site
  • ready-for-canonical-review
  • hold-in-raw
  • do-not-publish-yet