instructions/CONTRACT.md: Skill-H1, Referenztiefe und Begruendungsprosa praezisiert (schliesst #71, #72, #79)
Files changed: - CHANGES.md - VERSION - instructions/CONTRACT.md - instructions/wiki-ingest/SKILL.md
This commit is contained in:
@@ -24,13 +24,10 @@ pages should never have cost the concept contract. Field-level requirements alwa
|
||||
two capture flags are not: `raw accept` refuses without them.
|
||||
|
||||
**Ask the user for `--fidelity` and `--authority` before this call, rather than guessing from
|
||||
a quick look at the file.** This is the one place in the whole skill where the asymmetry from
|
||||
`source_type` (step 6 below) does not hold: a wrong `source_type` sits in a visible,
|
||||
correctable catalog slot (`unclassified`), but a guessed capture value is not "unknown" - it
|
||||
is a claim about the capture that cannot be corrected later, because the knowledge exists only
|
||||
at this drop point. If it is genuinely unclear how faithful the capture is or what the
|
||||
material may claim about its subject, say so to the user and ask directly - do not fall back
|
||||
to a plausible-looking default.
|
||||
a quick look at the file.** A guessed capture value is not "unknown": it is a claim about the
|
||||
capture that nothing later can correct, because the knowledge exists only at this drop point.
|
||||
Genuinely unclear how faithful the capture is, or what the material may claim about its
|
||||
subject? Say so and ask - there is no plausible-looking default to fall back on.
|
||||
|
||||
```bash
|
||||
tools/wikitool raw accept --fidelity <value> --authority <value> \
|
||||
@@ -79,7 +76,8 @@ pages should never have cost the concept contract. Field-level requirements alwa
|
||||
which entities/concepts to create or update, any specific emphasis.
|
||||
|
||||
6. **Create the source page.** Read
|
||||
[kb/sources/COLLECTION.md](../../kb/sources/COLLECTION.md) first.
|
||||
[kb/sources/COLLECTION.md](../../kb/sources/COLLECTION.md) first - it holds what this
|
||||
instance expects of a source page's sections and how it names one.
|
||||
|
||||
```bash
|
||||
tools/wikitool new source --name "<Title>" \
|
||||
@@ -99,12 +97,12 @@ pages should never have cost the concept contract. Field-level requirements alwa
|
||||
it later without moving or renaming the page.
|
||||
|
||||
`fidelity` and `authority` have no default either, and `new source` refuses without them the
|
||||
same way (Gitea #67) - but unlike `source_type` there is no catalog slot to fall back on. If
|
||||
step 1 already ran `raw accept` without `--page`, its success message printed the exact
|
||||
`--set fidelity=... --set authority=...` pair to reuse here verbatim; if it did not (the file
|
||||
was already in `raw/`), ask the user the same question step 1 asks before promoting, rather
|
||||
than inferring an answer from the file's content now. Never pass `unknown` here - that value
|
||||
is backfill-only, written only by `wikitool touch` on a page predating this rule.
|
||||
same way (Gitea #67) - but here there is no catalog slot to fall back on, for the reason step
|
||||
1 gives. If step 1 already ran `raw accept` without `--page`, its success message printed the
|
||||
exact `--set fidelity=... --set authority=...` pair to reuse here verbatim; if it did not (the
|
||||
file was already in `raw/`), ask the user, rather than inferring an answer from the file's
|
||||
content now. Never pass `unknown` here - that value is backfill-only, written only by
|
||||
`wikitool touch` on a page predating this rule.
|
||||
|
||||
List **every** raw file this ingest covers - a folder of related documents becomes one
|
||||
source page with all its files in `raw_files:`, not one page per file. For an external
|
||||
|
||||
Reference in New Issue
Block a user