Compare commits
No commits in common. "main" and "v1.2.0" have entirely different histories.
2 changed files with 1 additions and 19 deletions
|
|
@ -269,7 +269,7 @@ a green scan means safe content. The highest-impact items:
|
||||||
two of the three corpora are living, so the cells are not rewritten in place.
|
two of the three corpora are living, so the cells are not rewritten in place.
|
||||||
Method and before/after: [`docs/rawhtml-census.py`](docs/rawhtml-census.py).
|
Method and before/after: [`docs/rawhtml-census.py`](docs/rawhtml-census.py).
|
||||||
|
|
||||||
**Full list — 44 items, each with the mechanism, plus the out-of-scope boundary:**
|
**Full list — 43 items, each with the mechanism, plus the out-of-scope boundary:**
|
||||||
[`docs/LIMITATIONS.md`](docs/LIMITATIONS.md). Several carry field measurements from
|
[`docs/LIMITATIONS.md`](docs/LIMITATIONS.md). Several carry field measurements from
|
||||||
consumer corpora, including the false positives the URL-shape rule actually produces.
|
consumer corpora, including the false positives the URL-shape rule actually produces.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -98,24 +98,6 @@ items; this is the full list, each with the mechanism.
|
||||||
A concept whose `sources` are flat strings, or absent, imports. The
|
A concept whose `sources` are flat strings, or absent, imports. The
|
||||||
dangling-or-substituted `executor`/`attester` pointer question stays out of reach
|
dangling-or-substituted `executor`/`attester` pointer question stays out of reach
|
||||||
for the same reason: both are mappings whose payload key is `resource`.
|
for the same reason: both are mappings whose payload key is `resource`.
|
||||||
- **`tags` and `description` block the OKF import corpus universally, before the
|
|
||||||
trust layer is even reached.** The line-flat frontmatter parser has no
|
|
||||||
sequence-value type at all: `tags` is present in 53/53 upstream concept
|
|
||||||
documents — 9/53 as a flow sequence (`[a, b, c]`, rejected on the `[`
|
|
||||||
indicator) and 44/53 as a block sequence (`- a` / `- b`, rejected as
|
|
||||||
`"malformed frontmatter line"`) — 100% rejection regardless of form.
|
|
||||||
`description` is present in 53/53; 29/53 is a folded plain scalar continuing
|
|
||||||
on an indented second line, which the parser has no continuation-line model
|
|
||||||
for and misreads as `"nested mappings are not supported"` (the remaining
|
|
||||||
24/53 are single-line and parse fine). Measured directly on the upstream
|
|
||||||
reference bundles (`_okf-upstream/okf` @ `3fcbb9f`): removing `tags` alone
|
|
||||||
lets 4/53 documents pass; removing both `tags` and `description` together
|
|
||||||
(trust layer untouched) lets the same 4/53 pass, and all four then parse
|
|
||||||
`generated` correctly as a mapping. **Independent of both the mapping-form
|
|
||||||
gap and the `sources` block-form gap above:** closing either moves nothing
|
|
||||||
on this corpus, because `tags`/`description` reject before `sources` is ever
|
|
||||||
read. No sequence-value type or continuation-line model exists in the
|
|
||||||
stdlib-only parser to close this with.
|
|
||||||
- **A persist gate cannot cover execution risk.** OKF v0.2 introduces concepts whose
|
- **A persist gate cannot cover execution risk.** OKF v0.2 introduces concepts whose
|
||||||
purpose is to *name code to be run* (`runtime`, `executor.resource`,
|
purpose is to *name code to be run* (`runtime`, `executor.resource`,
|
||||||
`attester.resource`). This library answers "is this safe to **store**"; executable
|
`attester.resource`). This library answers "is this safe to **store**"; executable
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue