docs(data-engine): 1p extends the provenance chain to the network layer #3

2026-07-26T11:59:22Z

admin commented

2026-07-26 11:59:22 +00:00

Adds a subsection to docs/06-data-engine.md under "Confidence & provenance scoring" on 1p, the SIAX egress measurement point. Repo: https://git.siax.io/sax3l/1p

The gap it names. bridge_provenance answers which source a field came from. It does not answer what happened on the wire: which policy authorized the fetch, whether robots.txt was read and what it said, or whether the bytes we parsed were the page or a bot wall served with HTTP 200.

What 1p adds to claims 0pt already makes:

Claim	What 1p adds
"authorized public page, respecting robots.txt"	the robots decision plus a sha256 of the `robots.txt` it was taken from; a policy saying `respect` that cannot read robots denies the fetch
"these are the bytes we parsed"	`body_sha256` per fetch
"level 1/2/3 corroboration from independent sources"	`blocked_soft` detection — HTTP 200 whose body is a block page, which otherwise gets parsed and scored as corroborating data

Consistent with CLAUDE.md §1, not an exception to it. 1p is a measurement point, not a bypass: it exists to detect blocking and prove provenance. Its purchased-residential egress pool is an interface with a stub that throws; wiring it up would be a separate, explicit decision. Block detection alarms on a rising trend only, and excludes error (their 5xx, our timeouts) from the blocking measure. Background: a 2026-07-26 measurement across all scraper logs found 13 total "403" and 11 total "429" hits — self-throttled, not blocked.

Status: not in use. Phase 0 — code, contracts, tests; not deployed, no credentials. No 0pt worker routes through it and bridge_provenance remains the only provenance 0pt writes.

Documentation only. Written in English to match this repo's CLAUDE.md ("Tech docs + code identifiers in English").

Source choice: Gitea. sax3l/0pt on Gitea is 3 days ahead of GitHub (0eb47aa vs 5b72599).

🤖 Generated with Claude Code

Adds a subsection to `docs/06-data-engine.md` under "Confidence & provenance scoring" on **1p**, the SIAX egress measurement point. Repo: https://git.siax.io/sax3l/1p **The gap it names.** `bridge_provenance` answers *which source a field came from*. It does not answer what happened on the wire: which policy authorized the fetch, whether `robots.txt` was read and what it said, or whether the bytes we parsed were the page or a bot wall served with HTTP 200. **What 1p adds to claims 0pt already makes:** | Claim | What 1p adds | |---|---| | "authorized public page, respecting robots.txt" | the robots decision **plus a sha256 of the `robots.txt` it was taken from**; a policy saying `respect` that cannot read robots denies the fetch | | "these are the bytes we parsed" | `body_sha256` per fetch | | "level 1/2/3 corroboration from independent sources" | `blocked_soft` detection — HTTP 200 whose body is a block page, which otherwise gets parsed and scored as corroborating data | **Consistent with CLAUDE.md §1, not an exception to it.** 1p is a measurement point, not a bypass: it exists to *detect* blocking and *prove* provenance. Its purchased-residential egress pool is an interface with a stub that throws; wiring it up would be a separate, explicit decision. Block detection alarms on a rising trend only, and excludes `error` (their 5xx, our timeouts) from the blocking measure. Background: a 2026-07-26 measurement across all scraper logs found 13 total "403" and 11 total "429" hits — self-throttled, not blocked. **Status: not in use.** Phase 0 — code, contracts, tests; not deployed, no credentials. No 0pt worker routes through it and `bridge_provenance` remains the only provenance 0pt writes. Documentation only. Written in English to match this repo's CLAUDE.md ("Tech docs + code identifiers in English"). > **Source choice:** Gitea. `sax3l/0pt` on Gitea is 3 days ahead of GitHub (`0eb47aa` vs `5b72599`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

admin added 1 commit 2026-07-26 11:59:22 +00:00

docs(data-engine): 1p extends the provenance chain to the network layer

CI (SIAX Cloud) / security (push) Successful in 23s

Details

CI (SIAX Cloud) / quality (push) Successful in 40s

Details

CI (SIAX Cloud) / quality (pull_request) Successful in 42s

Details

CI (SIAX Cloud) / security (pull_request) Successful in 25s

Details

a06f86095f

bridge_provenance answers which source a field came from; it does not
answer what happened on the wire. 1p (the SIAX egress measurement point)
adds the robots decision + sha256 of the robots.txt it was read from,
body_sha256 per fetch, and blocked_soft detection — HTTP 200 whose body
is a block page, which otherwise gets scored as corroborating data.

Consistent with CLAUDE.md §1: a measurement point, not a bypass.
Documentation only; not in use, no worker routes through it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

admin added 1 commit 2026-08-09 08:48:44 +00:00

Merge remote-tracking branch 'origin/main' into docs/1p-egress-measurement-point

CI (SIAX Cloud) / quality (push) Successful in 41s

Details

CI (SIAX Cloud) / security (push) Successful in 21s

Details

CI (SIAX Cloud) / security (pull_request) Successful in 16s

Details

CI (SIAX Cloud) / quality (pull_request) Successful in 40s

Details

4cf833bb82

admin merged commit into main