---
record_id: HP-HTFOL-MASTER
classification: Historical Text FOL Master Rules
status: prototype
scope: Adaptor House governance rules for historical, translated, and difficult texts
---

# Historical Text FOL Master Rules

This master file defines the reusable FOL commentary layer. Individual projects such as De Jing, Dao Jing, the Thousand Character Classic, or Finnegans Wake may specialize it, but should not redefine its core vocabulary casually.

## Naming And Collision Rule

Do not use ambiguous short namespaces such as `dj` for project identity. `dj` can plausibly mean De Jing or Dao Jing.

Use explicit work namespaces:

| Work | Namespace |
| --- | --- |
| De Jing | `dejing` |
| Dao Jing | `daojing` |
| Dao De Jing received order | `daodejing` |
| De Dao Jing order | `dedaojing` |
| Thousand Character Classic | `qianziwen` |
| Finnegans Wake | `finneganswake` |

Record IDs may keep existing public paths for churn avoidance, but formal IDs should prefer the explicit namespace.

Examples:

```text
sentence_dejing_01_001
cl_dejing_01_001
cs_dejing_01_001_a
el_mlt_dejing_01_001
sentence_daojing_01_001
cl_daojing_01_001
```

## Master Layers

Every project should distinguish:

```text
SourceWork(w)
SourceUnit(u)
Sentence(s)
SentenceClaim(s, p)
FormalClaim(p)
ChineseLine(cl)
ChineseSegment(cs)
ChineseSyntaxModern(csm)
ChineseSyntaxArchaic(csa)
EnglishLine(el)
EnglishSegment(es)
EnglishSyntax(ex)
TranslationWitness(tw)
ProvisionalAlignment(a, b)
```

Projects may add language-specific or work-specific layers only in their own profile files.

## Soundness Requirements

1. Every formal claim declares quantifier scope.
2. Every formal claim has a proof sketch, proof reference, or explicit `Unproved(p)` marker.
3. Logical operators remain logical operators.
4. Predicate compounds must be justified by the lexicon; otherwise, split modifier and noun.
5. Translation witnesses do not become the sentence claim.
6. Public labels are human-readable; internal IDs remain metadata.
7. Work namespaces must be explicit enough to avoid collisions across projects.

## Churn Policy

Master changes should not regenerate page families directly. The safe order is:

1. Update master rules.
2. Update a project profile.
3. Update a single pilot record.
4. Run the project validator.
5. Regenerate only an explicit selected range.