P/prochal.pl
Current lens: WHITE ACTIVE

02 / SYSTEM DECISIONS

DECISIONS UNDER EVIDENCE.

A gated record of context, constraints, failure modes, trade-offs and verifiable outcomes.

01 / CONTENT GATEOWNER-APPROVED FACTS ONLY

PUBLICATION STATE / 00 APPROVED RECORDS

CONTENT
GATE ACTIVE.

No factual case record is emitted until its source, factual basis, anonymization and public wording are explicitly approved.

DRAFTS
VALIDATED / NOT RENDERED
PUBLIC OUTPUT
APPROVED + PUBLIC-SAFE ONLY
PROJECTIONS
WHITE / BLUE / RED
02 / DECISION RECORDREQUIRED PUBLIC STRUCTURE

Required system decision record fields

  1. 01CONTEXT
  2. 02CONSTRAINT
  3. 03FAILURE MODE
  4. 04DECISION
  5. 05TRADE-OFF
  6. 06RESULT
  7. 07LESSON
  8. 08EVIDENCE

This shell contains the publication contract only. It does not stand in for evidence and does not imply that a case has been approved.

03 / SYSTEM TRACEDOM + SVG / COMPLETE TEXT ALTERNATIVE

Illustrative system trace models

ILLUSTRATIVE / NON-PRODUCTION SYSTEM MODEL

TRACE IDENTITY.

An illustrative flow from subject intent through verification and an enforced decision.

IDENTITY BOUNDARY MODELIDLE / 00 OF 05
IDENTITY BOUNDARY MODEL Illustrative non-production visual supplement. The ordered text trace after this diagram contains the complete flow. DECLARES INTENTPRESENTS IDENTITYVERIFIES CONTEXTAPPLIES RESULT SUBJECTREQUEST ORIGINTRUST BOUNDARYDECISIONPROTECTED RESOURCE

ORDERED TEXT TRACE / IDENTITY

INFORMATION-EQUIVALENT
  1. 01
    SUBJECT

    A subject begins an identity-dependent action.

    TRACE ORIGIN
  2. 02
    REQUEST ORIGIN

    The request origin carries the declared identity intent.

    DECLARES INTENT
  3. 03
    TRUST BOUNDARY

    The trust boundary requires identity context to be verified.

    PRESENTS IDENTITY
  4. 04
    DECISION

    A decision applies the verified context to explicit rules.

    VERIFIES CONTEXT
  5. 05
    PROTECTED RESOURCE

    The result is enforced before the protected resource is reached.

    APPLIES RESULT

FAILURE MODES

  • ASSERTION NOT VERIFIED
  • DECISION CONTEXT INCOMPLETE
  • ENFORCEMENT RESULT NOT APPLIED

EVIDENCE POINTS

  • VERIFICATION RESULT
  • POLICY DECISION
  • BOUNDARY EVENT

ILLUSTRATIVE / NON-PRODUCTION SYSTEM MODEL

TRACE REQUEST.

An illustrative request flow from origin through routing, handling and a returned result.

REQUEST BOUNDARY MODELIDLE / 00 OF 05
REQUEST BOUNDARY MODEL Illustrative non-production visual supplement. The ordered text trace after this diagram contains the complete flow. EMITS REQUESTCROSSES BOUNDARYDISPATCHES WORKRETURNS RESULT CALLERREQUEST EDGESERVICE BOUNDARYREQUEST HANDLERRESPONSE RESULT

ORDERED TEXT TRACE / REQUEST

INFORMATION-EQUIVALENT
  1. 01
    CALLER

    A caller begins a bounded request.

    TRACE ORIGIN
  2. 02
    REQUEST EDGE

    The request edge receives the incoming operation.

    EMITS REQUEST
  3. 03
    SERVICE BOUNDARY

    The service boundary applies entry and routing rules.

    CROSSES BOUNDARY
  4. 04
    REQUEST HANDLER

    The request handler performs the selected operation.

    DISPATCHES WORK
  5. 05
    RESPONSE RESULT

    A response result closes the request path.

    RETURNS RESULT

FAILURE MODES

  • ROUTE NOT RESOLVED
  • BOUNDARY RULE REJECTS REQUEST
  • HANDLER RESULT NOT RETURNED

EVIDENCE POINTS

  • CORRELATION RECORD
  • ROUTE DECISION
  • RESPONSE STATUS

ILLUSTRATIVE / NON-PRODUCTION SYSTEM MODEL

TRACE EVENT.

An illustrative event flow from a change origin through delivery and an acknowledged processing result.

EVENT DELIVERY MODELIDLE / 00 OF 05
EVENT DELIVERY MODEL Illustrative non-production visual supplement. The ordered text trace after this diagram contains the complete flow. EMITS EVENTACCEPTS EVENTDELIVERS EVENTRECORDS RESULT PRODUCEREVENT BOUNDARYEVENT CHANNELCONSUMERPROCESSING RESULT

ORDERED TEXT TRACE / EVENT

INFORMATION-EQUIVALENT
  1. 01
    PRODUCER

    A producer emits a described change.

    TRACE ORIGIN
  2. 02
    EVENT BOUNDARY

    The event boundary decides whether the change is accepted.

    EMITS EVENT
  3. 03
    EVENT CHANNEL

    The event channel carries the accepted record.

    ACCEPTS EVENT
  4. 04
    CONSUMER

    A consumer handles the delivered event.

    DELIVERS EVENT
  5. 05
    PROCESSING RESULT

    The processing result closes the observable event path.

    RECORDS RESULT

FAILURE MODES

  • EVENT NOT ACCEPTED
  • DELIVERY RETRIED OR EXHAUSTED
  • PROCESSING RESULT NOT RECORDED

EVIDENCE POINTS

  • PUBLISH RESULT
  • DELIVERY ATTEMPT
  • PROCESSING ACKNOWLEDGEMENT

ILLUSTRATIVE / NON-PRODUCTION SYSTEM MODEL

TRACE DELIVERY.

An illustrative delivery flow from a source change through verification, promotion and a recorded result.

DELIVERY CONTROL MODELIDLE / 00 OF 05
DELIVERY CONTROL MODEL Illustrative non-production visual supplement. The ordered text trace after this diagram contains the complete flow. SUBMITS CHANGEVERIFIES BUILDPROMOTES ARTIFACTAPPLIES RELEASE SOURCE CHANGEBUILD BOUNDARYRELEASE ARTIFACTENVIRONMENT GATEDELIVERY RESULT

ORDERED TEXT TRACE / DELIVERY

INFORMATION-EQUIVALENT
  1. 01
    SOURCE CHANGE

    A source change identifies the intended system modification.

    TRACE ORIGIN
  2. 02
    BUILD BOUNDARY

    The build boundary verifies the change before promotion.

    SUBMITS CHANGE
  3. 03
    RELEASE ARTIFACT

    The release artifact carries a stable identity.

    VERIFIES BUILD
  4. 04
    ENVIRONMENT GATE

    The environment gate makes the release decision explicit.

    PROMOTES ARTIFACT
  5. 05
    DELIVERY RESULT

    The delivery result records how release application ended.

    APPLIES RELEASE

FAILURE MODES

  • BUILD VERIFICATION FAILED
  • ARTIFACT IDENTITY MISMATCH
  • ENVIRONMENT GATE REJECTED RELEASE

EVIDENCE POINTS

  • SOURCE REVISION
  • ARTIFACT DIGEST
  • DEPLOYMENT RESULT

ILLUSTRATIVE / NON-PRODUCTION SYSTEM MODEL

TRACE FAILURE.

An illustrative failure flow from signal through containment, diagnosis and verified recovery.

FAILURE RESPONSE MODELIDLE / 00 OF 05
FAILURE RESPONSE MODEL Illustrative non-production visual supplement. The ordered text trace after this diagram contains the complete flow. RAISES SIGNALCLASSIFIES FAILURELIMITS SPREADVERIFIES RECOVERY FAILURE SIGNALDETECTIONCONTAINMENT BOUNDARYDIAGNOSISRECOVERY EVIDENCE

ORDERED TEXT TRACE / FAILURE

INFORMATION-EQUIVALENT
  1. 01
    FAILURE SIGNAL

    A failure signal makes abnormal behavior visible.

    TRACE ORIGIN
  2. 02
    DETECTION

    Detection classifies the observed signal.

    RAISES SIGNAL
  3. 03
    CONTAINMENT BOUNDARY

    The containment boundary limits further spread.

    CLASSIFIES FAILURE
  4. 04
    DIAGNOSIS

    Diagnosis forms and tests a cause hypothesis.

    LIMITS SPREAD
  5. 05
    RECOVERY EVIDENCE

    Recovery evidence verifies the resulting state.

    VERIFIES RECOVERY

FAILURE MODES

  • SIGNAL IGNORED
  • CONTAINMENT INEFFECTIVE
  • RECOVERY NOT VERIFIED

EVIDENCE POINTS

  • DETECTION RECORD
  • CONTAINMENT ACTION
  • RECOVERY CHECK
04 / INCIDENT LAYERSIMULATED / ANONYMIZED / NO LIVE STATUS

Simulated and anonymized Incident Layer

SIMULATED / ANONYMIZED ENGINEERING TRACE

INCIDENT REHEARSED.

A bounded rehearsal follows a synthetic certificate-expiry signal from detection to verified recovery.

DATA
SYNTHETIC SIGNALS ONLY
SCOPE
ISOLATED REHEARSAL
IDENTIFIERS
GENERIC ROLES
STATUS CLAIM
NO LIVE SYSTEM STATUS
  1. T+00DETECT

    EXPIRY THRESHOLD SIGNAL

    The rehearsal begins when a synthetic validity window crosses its defined threshold.

    ROLE
    SCENARIO MONITOR
    BOUNDARY
    OBSERVATION BOUNDARY
    EVIDENCE
    SYNTHETIC VALIDITY WINDOW / SIMULATED ALERT RECORD
  2. T+04CLASSIFY

    SCOPE AND IMPACT HYPOTHESIS

    The coordinator confirms the exercise scope before selecting a response path.

    ROLE
    INCIDENT COORDINATOR
    BOUNDARY
    DECISION BOUNDARY
    EVIDENCE
    SCENARIO SCOPE RECORD / IMPACT HYPOTHESIS
  3. T+09CONTAIN

    TEST PATH ISOLATED

    The affected rehearsal path is held inside the isolated scenario boundary.

    ROLE
    EDGE OPERATOR
    BOUNDARY
    TRAFFIC BOUNDARY
    EVIDENCE
    ISOLATION DECISION / TEST ROUTE STATE
  4. T+15RECOVER

    REPLACEMENT APPLIED

    A replacement test certificate is applied through the defined rehearsal procedure.

    ROLE
    CERTIFICATE OPERATOR
    BOUNDARY
    CHANGE BOUNDARY
    EVIDENCE
    CHANGE RECORD / SYNTHETIC CERTIFICATE DIGEST
  5. T+21VERIFY

    RECOVERY EVIDENCE ACCEPTED

    The exercise closes only after the expected trust path and validity checks succeed.

    ROLE
    INDEPENDENT VERIFIER
    BOUNDARY
    RECOVERY BOUNDARY
    EVIDENCE
    VERIFICATION CHECKLIST / SCENARIO RECOVERY RESULT
EXERCISE END STATE

Recovery is accepted only after independent scenario evidence satisfies the defined checks. This model reports no operational status.

05 / NO ABSTRACTIONSCOMPONENT / MECHANISM / BOUNDARY / EVIDENCE / FAILURE

CHAIN EXPOSED.

Four illustrative system paths name what acts, how it acts, where responsibility changes, what can be observed and how each stage can fail.

CHAIN 01 / 04

IDENTITY DECISION CHAIN

Identity becomes access only after assertion, policy and enforcement boundaries produce evidence.

SUBJECT / ISSUER / POLICY / ENFORCER / RESOURCE
  1. 01

    SUBJECT AGENT

    OIDC authorization request

    BOUNDARY
    AGENT TO IDENTITY EDGE
    EVIDENCE
    CORRELATION ID
    FAILURE
    REQUEST CONTEXT REJECTED
  2. 02

    IDENTITY ISSUER

    Factor verification and signed assertion

    BOUNDARY
    TRUST ISSUANCE
    EVIDENCE
    AUTHENTICATION EVENT + ASSERTION ID
    FAILURE
    ASSERTION NOT ISSUED
  3. 03

    POLICY DECISION POINT

    Claim, context and policy evaluation

    BOUNDARY
    AUTHORIZATION DECISION
    EVIDENCE
    POLICY REVISION + DECISION RECORD
    FAILURE
    POLICY DENIES OR CANNOT EVALUATE
  4. 04

    RESOURCE ENFORCER

    Decision validation and action gating

    BOUNDARY
    ENFORCEMENT
    EVIDENCE
    ENFORCEMENT EVENT
    FAILURE
    DECISION INVALID OR EXPIRED
  5. 05

    PROTECTED RESOURCE

    Authorized operation execution

    BOUNDARY
    RESOURCE OWNERSHIP
    EVIDENCE
    OPERATION RESULT
    FAILURE
    RESOURCE OPERATION FAILS
CHAIN 02 / 04

CERTIFICATE TRUST CHAIN

Certificate trust depends on validated control, issued identity, deployed material and peer verification.

NAME / ACME / CA / EDGE / VERIFIER
  1. 01

    SERVICE NAME

    ACME order for a declared identifier

    BOUNDARY
    IDENTIFIER OWNERSHIP
    EVIDENCE
    ORDER ID + REQUESTED NAMES
    FAILURE
    ORDER DOES NOT MATCH INTENDED NAME
  2. 02

    ACME CHALLENGE

    DNS-01 or HTTP-01 control proof

    BOUNDARY
    DOMAIN CONTROL
    EVIDENCE
    CHALLENGE RESULT
    FAILURE
    CONTROL PROOF NOT OBSERVABLE
  3. 03

    CERTIFICATE AUTHORITY

    X.509 issuance and chain construction

    BOUNDARY
    TRUST ISSUANCE
    EVIDENCE
    CERTIFICATE SERIAL + ISSUER CHAIN
    FAILURE
    ISSUANCE REJECTED
  4. 04

    TLS TERMINATION EDGE

    Certificate and matching key deployment

    BOUNDARY
    KEY STORAGE TO RUNTIME
    EVIDENCE
    DEPLOYMENT REVISION + CERTIFICATE DIGEST
    FAILURE
    IDENTITY OR KEY MISMATCH
  5. 05

    TLS VERIFIER

    Name, validity and chain verification

    BOUNDARY
    PEER TRUST
    EVIDENCE
    TLS HANDSHAKE RESULT
    FAILURE
    CHAIN OR NAME VALIDATION FAILS
CHAIN 03 / 04

REQUEST EXECUTION CHAIN

A request becomes a response through explicit transport, routing, execution and result boundaries.

ORIGIN / TLS EDGE / ROUTER / HANDLER / RESPONSE
  1. 01

    HTTP ORIGIN

    Method, path, headers and bounded body

    BOUNDARY
    EXTERNAL ORIGIN
    EVIDENCE
    REQUEST ID
    FAILURE
    REQUEST CANNOT BE FORMED
  2. 02

    TLS EDGE

    TLS handshake and HTTP protocol acceptance

    BOUNDARY
    NETWORK INGRESS
    EVIDENCE
    HANDSHAKE + CONNECTION RESULT
    FAILURE
    TRANSPORT REJECTED
  3. 03

    REVERSE PROXY

    Host-independent route and policy match

    BOUNDARY
    ROUTING CONTROL
    EVIDENCE
    ROUTE ID + UPSTREAM DECISION
    FAILURE
    NO SAFE ROUTE
  4. 04

    REQUEST HANDLER

    Input validation and operation execution

    BOUNDARY
    APPLICATION OWNERSHIP
    EVIDENCE
    OPERATION SPAN + RESULT
    FAILURE
    VALIDATION OR DEPENDENCY FAILURE
  5. 05

    HTTP RESPONSE

    Status, headers and bounded representation

    BOUNDARY
    OUTBOUND CONTRACT
    EVIDENCE
    STATUS + COMPLETION RECORD
    FAILURE
    RESULT NOT SERIALIZED OR RETURNED
CHAIN 04 / 04

EVENT DELIVERY CHAIN

An event is useful only when publication, delivery, processing and acknowledgement remain traceable.

PRODUCER / OUTBOX / CHANNEL / CONSUMER / ACK
  1. 01

    EVENT PRODUCER

    Versioned event creation

    BOUNDARY
    CHANGE ORIGIN
    EVIDENCE
    EVENT ID + SCHEMA VERSION
    FAILURE
    EVENT CANNOT BE CREATED
  2. 02

    TRANSACTIONAL OUTBOX

    State change and event record committed together

    BOUNDARY
    TRANSACTION
    EVIDENCE
    COMMIT RECORD + OUTBOX ID
    FAILURE
    STATE AND EVENT DIVERGE
  3. 03

    EVENT CHANNEL

    Publish, retention and retry policy

    BOUNDARY
    DELIVERY OWNERSHIP
    EVIDENCE
    PUBLISH ACK + DELIVERY ATTEMPT
    FAILURE
    DELIVERY EXHAUSTED
  4. 04

    IDEMPOTENT CONSUMER

    Schema validation and deduplicated handling

    BOUNDARY
    CONSUMER OWNERSHIP
    EVIDENCE
    CONSUMPTION ID + OPERATION RESULT
    FAILURE
    SCHEMA OR HANDLER REJECTS EVENT
  5. 05

    PROCESSING ACK

    Offset or message acknowledgement after success

    BOUNDARY
    PROCESSING COMPLETION
    EVIDENCE
    ACK POSITION + COMPLETION TIME
    FAILURE
    SUCCESS NOT ACKNOWLEDGED