Incident references

The write gate (pre-write-edit) refuses a write that puts a pointer into the internal defect register or transcript store into product code or a public page. Such a pointer tells a reader nothing they can follow, and on a product's site it publishes the operator's internal history. Why a line or a page exists is said in the product's own terms; the incident stays in Oko.

#What is refused

• defect or session followed by an eight-character hexadecimal identifier;
• a bare agent session identifier (01a0xxxx-xxxx…);
• a session-numbered message (01a0xxxx #N).

#Where

• Product code: .rs, .swift, .ts, .tsx, .js, .mjs, .cjs, .py, .sh, .go, .kt, .java, .c, .h, .m, .mm, .cpp.
• Public pages: every file in a product's site repository (a path containing -landing/), and any repository's README.md and CHANGELOG.md.

Private notes outside those places, such as workshop rules, are not judged. Like every content rule of pre-write-edit, this one judges the whole file a write leaves, lines it already held included (whole-file judgement).

#Spelled-out addresses and fleet machines

In the same places the gate refuses an IPv4 address, a user-at-host destination, a loopback name with a port, and a machine name or hostname the fleet registry copy (~/.stado/cache/registry-last-good.json) declares. Read the value from where it is declared: the Stado registry, the service directory or the product's configuration. An example uses a host under a reserved example domain (.example, .invalid, .test, example.com, example.net, example.org), or an IPv4 address in a block RFC 5737 reserves for documentation (TEST-NET-1, TEST-NET-2, TEST-NET-3), which the gate admits; the journey is a_documentation_range_address_names_no_host in tests/content/addresses.rs.

What follows the at sign names a host only when its last label is not all digits, because no top-level domain is all digits. A font axis weight in a stylesheet request and a package pinned to a release version are therefore not addresses, and a page that loads its fonts that way can be edited. The journey is an_all_digit_label_after_at_names_no_host in tests/content/addresses.rs.

A dotted quad that stands in a version is not an address either: right after a product name and a slash (Chrome/<major>.0.0.0, the product token of a user agent) or right after a regular expression's back-reference spliced into one ('Chrome/$1 followed by .0.0.0'), it names a release. The same quad as a URL's host (after //) or standing alone is still refused. The journey is a_quad_in_a_version_token_names_no_host_and_one_in_a_url_does in tests/content/addresses.rs.

pre-write-edit: BLOCKED: `<address>` is hardcoded data: an address or a fleet machine spelled into the file. …

#The refusal

pre-write-edit: BLOCKED: `session <ID>` points into the internal defect register or transcript store. …

Remove the reference and state what the product guarantees. Record the incident with oko defects record or oko defects note.

#Where the refusal comes from

Source: rust/crates/tama-hook-tools/src/ports/pre_write_edit/content/incidents.rs, run by tama hook pre-write-edit; installed with DEVICE_HOOK_EDIT_APPROVED=1 tama hooks release.