Phase A — http-capability-gateway↔BoJ contract, policy workflow, example spec#74
Draft
hyperpolymath wants to merge 1 commit into
Draft
Phase A — http-capability-gateway↔BoJ contract, policy workflow, example spec#74hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
…xample Verb Governance Spec
Phase A of the http-capability-gateway tier-2 wiring programme
(ADR 0004 / docs/integration/http-capability-gateway-plan.md).
A1: docs/integration/http-capability-gateway-boj-contract.md — the
normative HTTP contract between the gateway (front) and BoJ's
unified Zig API gnosis handler (back): transport, port allocation,
forwarded headers, the X-Trust-Level trusted-proxy invariant, and
error/circuit-breaker semantics.
A2: docs/integration/http-capability-gateway-policy-workflow.md —
the Verb Governance Spec authoring, review, load, and hot-reload
workflow.
A3: config/gateway-policy-boj-example.yaml — a DSL v1 example policy
derived from docs/specification/openapi.yaml, conforming to the
schema documented in the integration audit §2.
Documentation only. No gateway or BoJ code changed; the example
policy is not loaded by any running service. Build is unaffected.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase A — Contract Definition (weeks 1–2)
First materially-advancing PR of the http-capability-gateway tier-2 wiring
programme. Delivers all three Phase A artefacts from
docs/integration/http-capability-gateway-plan.md. Documentation only — nogateway or BoJ code changed; the build is unaffected (plan acceptance
criterion: "No code changes to gateway or BoJ gnosis handler").
Deliverables
docs/integration/http-capability-gateway-boj-contract.md— thenormative gateway↔BoJ HTTP contract. Resolves the Phase A transport
indecision risk (staging = TCP loopback :7700; production = Unix socket
preferred, TCP fallback), enumerates the forwarded-header set, and states
the
X-Trust-Leveltrusted-proxy invariant as RFC-2119 MUSTs handed toPhase C as seam-test obligations. Fail-closed error/circuit-breaker
semantics documented.
docs/integration/http-capability-gateway-policy-workflow.md— wherethe Verb Governance Spec lives (
config/gateway-policy.yaml, this repo),the authorship + review + openapi-coupling gate, the validation procedure,
the k9-svc rolling-redeploy hot-reload path, and the
global_verbsdefault-public sharp edge with BoJ's default-deny mitigation.
config/gateway-policy-boj-example.yaml— a DSL v1 worked examplederived route-by-route from
docs/specification/openapi.yaml, conformingto the schema in the integration audit §2. Example/fixture only; no service
loads it.
Scope note
This session's GitHub tool scope is restricted to
hyperpolymath/boj-serverand
hyperpolymath/http-capability-gateway;hyperpolymath/standardsis notreachable from here, so the standards issues could not be read or commented
on directly. Phase A lands entirely in
boj-serverper the plan, so the workitself is unaffected; the issue references below are recorded for tracking.
Refs hyperpolymath/standards#91
Closes hyperpolymath/standards#96
🤖 Generated with Claude Code
Generated by Claude Code