Tags

Tags give the ability to mark specific points in history as being important

  • v0.3.0

    48ad613d · Changelog and version for 0.3.0 · 
    egress 0.3.0

The catalog gains its sibling: the east-west map answers which of the
operator's own components opens each connection when firewall zones
split them.

Added: the /east-west/ page — a zone-seam map (five zones, nine
directed seams, arrowhead on the responder, port and protocol on
every edge) and the rule-writing table (initiator, responder, port
and protocol, trigger, cadence, allow rule, blocked-failure
signature, citations), with two first-class verified negatives: no
inbound connections to the runner or the workstation, ever. New
interconnect record type with its own schema, per deployment form,
under the cross-deployment consistency gate and the freshness
tripwire. All nine seams derived from public source and documentation
at pinned refs, including the canonical reverse edge (the self-hosted
AI gateway fetches token-verification keys from the instance; block
it and every Duo request fails) and the Workhorse fact (the
workstation never dials the Duo Workflow Service's port 50052).
Navigation gains the sibling pair and each map cross-links the other;
a shared-geometry conformance check fails the build on any geometry
defect. PRD R13; RFC-0001 interconnect records; RFC-0003 c21.

Changed: the section sidebar carries the open page's own second-level
headings, nested under the active entry and built in the permalink
pass so it cannot drift. PRD rendering item 15.

Fixed: the renderings census names all four views (egress map,
east-west map, reference table, machine-readable text) on every
census surface — landing, where-to-go, method overview, README — with
a standing rule that a new rendering lands in every census surface in
the same change. PRD rendering item 14.

  • v0.2.0

    43138e48 · Changelog and version for 0.2.0 · 
    egress 0.2.0

The machine-readable text rendering joins the map and the table, and a
visual-placement pass on the map lands with permanent conformance
enforcement.

Added
- llms.txt and llms-full.txt generated from the profile data at build
  time (llmstxt.org convention). llms.txt indexes the site's pages and
  all eleven modalities; llms-full.txt is the complete catalog as
  plain text: 108 destination entries across both deployment trees
  with class, state, scenarios, trigger, control, full mitigation, and
  provenance, prefixed by the classification vocabulary. Deterministic
  output; the hand-written stub is retired. PRD rendering item 13.

Changed
- Map header: the section title matches the site name at 15px; the
  brand line reads as one unit. RFC-0003 c17 refined.

Fixed
- Map: the workstation caption anchors over its own zone instead of
  the canvas center. Check-enforced: capMisanchors MUST 0. RFC-0003
  c19 extended.
- Map: the empty-state reminder is width-bounded and wraps to multiple
  lines, clear of the left-column geometry. Check-enforced: hintHits
  MUST 0. RFC-0003 c18 refined.

Commits: ddc32f1 (added), 8478eb0 (changed), 75e3cb8 (fixed),
43138e4 (release prep). Pipeline green on the tagged commit; all
fixes live-verified on Pages before tagging.

  • v0.1.1

    75730d12 · Changelog and version for 0.1.1 · 
    egress v0.1.1

Fixed

- Map: hidden component pills stay hidden in every interaction state.
  Scenario-parked pills relied on being invisible while parked on
  slots active pills occupy; the focus-isolation style re-opacified
  them during hover and selection, superimposing two pills
  (reader-reported: ClickHouse over the Duo Workflow Service pill).
  The hide rule now carries an importance floor, the conformance
  check counts active-pill collisions (pillOverlaps, zero required),
  and RFC-0003 constraint 16 covers interior pills in every
  interaction state.

Full notes: CHANGELOG.md.

  • v0.1.0

    35b45fbf · Changelog for 0.1.0 · 
    egress v0.1.0

First release: the complete profile of what a self-managed GitLab
instance sends outbound, as evidence-backed data with two renderings
and the machinery to keep it true.

- Profile data: 54 destinations x 2 deployment trees (Omnibus, Cloud
  Native), schema-validated, consistency-gated; every destination
  carries provenance, a verification ledger, attribution, a content
  class, its default state, and a required mitigation entry.
- Operator-installed components (self-hosted AI gateway, Duo Workflow
  Service, ClickHouse) answer for their own outbound surface,
  including verified negatives.
- Interactive trust-boundary map with three AI-inference scenarios
  and a per-render conformance check; reference table fitted to a
  laptop viewport; documentation site with a method overview and a
  live map embed.
- Freshness tripwire: scheduled CI reds when the data falls behind
  the re-derivation cadence, pinned evidence drifts, or a citation
  rots; re-verification stays a supervised session.
- Decision corpus: PRD, RFC-0001..0003, ADR-0001..0011.

Full notes: CHANGELOG.md.