Skip to content

docs(design): define Zetesis acquisition boundary - #69

Merged
forkwright merged 1 commit into
mainfrom
docs/zetesis-acquisition-boundary
Aug 26, 2026
Merged

docs(design): define Zetesis acquisition boundary#69
forkwright merged 1 commit into
mainfrom
docs/zetesis-acquisition-boundary

Conversation

@forkwright

@forkwrightforkwright commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • assign invocation authorization, tenant/session/grant/budget/credential context, persistence, browser behavior, and audit to Dioptron
  • assign the consumer-neutral validated-target, redirect-proof, bounded-transfer, static-extraction, and evidence-envelope state machine to Zetesis
  • specify an adapter sequence that reserves authority with durable intent, invokes an exact pinned producer, stores its envelope verbatim with Dioptron identities, then settles or releases
  • forbid a second HTTP, redirect, SSRF, decompression, extraction, or evidence-construction path in the adapter
  • keep dependency and adapter work gated on a merged immutable Zetesis SHA registered or derived through Kanon and a real consumer compatibility test

Scope

This is a design and structured-corpus change. It adds no dependency or Cargo manifest, lockfile, Rust code, import, adapter implementation, or workflow change. The existing implementation tracker and its Done-when conditions remain open.

The anonymous static GET boundary is independent of paid-provider accounting. Dioptron still reserves its invocation resources, while paid provider calls retain their separate atomic budget requirement.

Verification

  • ci/check-doc-manifest.py . — 12 canonical documents validated
  • ci/check-doc-refs.py . — 18 Markdown files scanned
  • Python tomllib parse of the touched TOML files
  • git diff --check

No build was run because this repository and change are docs-only.

Refs #66

forkwright added a commit that referenced this pull request Aug 26, 2026
## Summary
- replace Dioptron's trailer-only workflow with the first-party hybrid
gate, including pull-request and push-to-main verification and the
terminal `gate / gate` context
- run every honest public docs-phase mechanism on untrailed changes:
Python syntax, numbered-reference resolution, manifest completeness, and
structural negative fixtures
- keep `kanon lint --workflow`, README writing lint, and
manifest-derived writing lint explicitly forge-only instead of claiming
hosted GitHub ran a private binary
- add the canonical Dependabot auto-merge caller and update contributor
guidance to describe the hybrid contract
## Verification contract
The PR itself is the first exact-head execution of the new hosted path.
No local build, test, or gate command ran on Metis. The only local
mechanical check was `git diff --check`.
Dioptron has no Cargo workspace. The reusable's required command slots
therefore carry real Python/document checks rather than vacuous `true`
commands; the optional doctest slot is empty because it is structurally
inapplicable.
## Collision inventory
- PR #65 owns only `.github/workflows/release-pr-checks.yml`; this
branch does not add or edit that file.
- PR #67 changes one checkout-version comment inside the legacy gate
implementation. This branch removes that checkout step with the legacy
implementation, so #67's one-line path change becomes obsolete rather
than being copied into dead machinery.
- PRs #68 and #69 are path-disjoint. PR #69's worktree was not touched.
## Honest residual
The shared Dependabot reusable currently requires Cargo security-check
groups (`cargo deny`, `cargo audit`, and OSV) in addition to the
terminal gate. A docs-only non-Cargo repository cannot emit those
honestly. The new caller therefore fails closed for Dependabot until the
reusable accepts a repository-specific verification contract; this PR
does not manufacture vacuous Cargo jobs to make auto-merge appear
functional.
The shared hybrid workflow also installs Rust/nextest runner substrate
unconditionally. That is harmless but unnecessary overhead for
Dioptron's present non-Cargo phase and belongs in the reusable, not a
local fork.
Refs #67.
Co-authored-by: forkwright <cody@forkwright.com>
@forkwright
forkwright marked this pull request as draft August 26, 2026 21:11
forkwright added a commit that referenced this pull request Aug 26, 2026
## Summary
- remove the Dependabot caller that cannot function in a non-Cargo
repository
under the shared Cargo-only verification contract
- make GitHub the authoritative repository, pull-request, review, CI,
and merge
surface in contributor guidance
- describe `.kanon-ci.toml` as a supplementary local Kanon recipe, not a
live
forge pipeline or independent merge verifier
## Verification
No local build, test suite, or Kanon gate ran on Metis. `git diff
--check` passed
on `acb496e15591e1e6899a04b8cf44e543b4268ad9`. This draft's public
GitHub run is
the first exact-head execution of the active verifier.
## Tracker and authority
- Refs #70, whose merged caller and docs created the corrected surface.
- Refs #72 for the operator-owned eventual `gate / gate`
branch-protection
requirement. This PR does not mutate repository authority.
- Refs forkwright/.github#64 for a typed non-Cargo Dependabot
verification
profile.
- Refs forkwright/.github#65 for a command-only hybrid-gate runner
profile.
## Collision inventory
- The branch is rooted at merged #70 commit
`8b3fbe8b7c34355498a26f6870b6ac5235a29738` and does not reuse #70's
deleted
head branch.
- PR #67's sole legacy-workflow comment change was re-verified as
present in
#70's replacement workflow, then #67 was closed with the exact
supersession
evidence.
- Open PRs #65, #68, #69, and release PR #71 do not change these three
paths.
## Honest residual
`main` currently has zero required status contexts. Issue #72
deliberately
sequences the operator-owned protection change after every surviving
stale PR
emits the genuine `gate / gate` context on its current head.
Dependabot auto-merge remains absent in Dioptron until the shared
reusable has a
real non-Cargo contract. No vacuous Cargo jobs substitute for that
missing
mechanism.
---------
Co-authored-by: forkwright <cody@forkwright.com>
@forkwright
forkwrightforce-pushed the docs/zetesis-acquisition-boundary branch from fe37893 to fd2f7ffCompareAugust 26, 2026 21:47
@forkwright
forkwright marked this pull request as ready for review August 26, 2026 21:52
@forkwright
forkwright merged commit a9d9f74 into mainAug 26, 2026
5 checks passed
@forkwright
forkwright deleted the docs/zetesis-acquisition-boundary branch August 26, 2026 21:52
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@forkwright