Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

OPS.3:5 - Archetypal Grounding — PumpWorks Subject Account

The weekly release decision initially sees four cards and a rig calendar. To decide what can be relied on, distinguish the cards and calendar from the following subjects and relations:

Visible itemRecovered subject or relationRecord boundary
ReleaseCandidate-R42 cardA release-candidate subject and its candidate contents, required evidence results, release Work items, and receiving release decision.The card and commit identifiers are records; moving the card does not change deployed field state or satisfy the release commitment.
FieldIncident-I73 ticketA case organized around FieldPumpInstallation-P4, reported symptoms, service commitments, evidence, authority, permissible next Work, and closure conditions.Ticket closure does not establish restored field condition or fulfilled service.
SafetyQuestion-S19 issueA question episteme, related evidence needs, specialist safety decision, and any Work items created to obtain that result.A red label is neither a safety state nor authority to accept risk.
ProviderChange-P8 epicA time-bounded change subject with provider relations, access conditions, project WorkPlan content, affected release cases, and decisions.The epic does not make the provider part of PumpWorks or prove performed migration Work.
test-rig booking rowQueue membership of an exact eligible request for resource relation to TestRig-2, with interval, order/policy, access condition, and status evidence.The booking row records planned access. Establish request eligibility, allocation authority, performed test Work, and test completion separately.

Distinguish the records for this decision: ticket, trace, source commit, build result, test result, service log, field-engineer report, telemetry record, and release decision each support bounded claims. A multi-object event record may relate one event to several subjects, but it does not identify those subjects with one case or prove the represented Work.

Consider a later, constructed PumpWorks reconciliation. An imported test event L17 has been associated with both R41 and R42 because their records share a release folder. The board consequently removes R42’s test request from the ready queue and reports “tested at 10:20.” That conclusion assumes that L17 tested R42, and that 10:20 is test completion rather than receipt of the message.

The lab’s signed execution record identifies the tested build as R41 and completion at 09:50; the intake trace identifies 10:20 as message receipt. The lab engineer confirms those meanings, and the authorized record maintainer replaces the false R42 association with the supported R41 association while retaining the original import and the correction’s basis. R42’s completion claim is withdrawn. After confirming that R42’s independently established inputs and permission still hold, the scheduler restores its waiting eligibility and the priority justified by the current queue rule and original waiting history. Correction time does not restart its age or revoke work already permitted or performed on other requests. L17 supports the stated R41 test result, not R41’s wider release or field condition.

S19’s unresolved safety question, I73’s field observations and the independently permitted work on them remain as they were. The correction reaches OPS.4’s R42 state and OPS.8’s test population because those uses consumed the bad link; it does not invalidate the entire operating account. If the execution record cannot identify the tested build, neither R41 nor R42 acquires test completion from L17. Ask the lab which build the record covers, or identify that missing fact in the result. Other work can proceed where its independent conditions and permissions hold. This small reconciliation is sufficient when those are the only affected uses; a full data-model migration would add cost without changing the decision.

For the product-side control view, FieldPumpInstallation-P4, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 retain their relation-specific meanings. For operating supervision, ReleaseSupervisorTeam-S2 is an admitted acting System only where supported and the two-sided report/constraint relation to PumpWorks-ControlServiceOps is recorded only if both sides obtain. The diagram, participants, relations, state claims, and operating account remain distinct.

When participants need a shared or maintained account, use these subjects, records, current claims and any relevant conflicts, permissions or update conditions in OPS.4. Reopen only the affected identity or relation when a release candidate is superseded, an incident splits or merges under an explicit rule, a queue membership changes, a record source becomes stale, or a claimed control relation loses one side.