Architecture & Decision Register

Solution architecture

Source systems own their records. The readiness layer owns the integrated decision context.

[Aconex]  [P6]  [Q4/Entity Desk]  [Forwood]  [People/Training]  [Health flag]
    |       |          |             |              |               |
    +-------+----------+------+------+--------------+---------------+
                              |
                   Integration adapters (mock)
     SourceSystem · ObjectID · Revision · LastVerified · WriteAuthority
                              |
        Readiness core: applicability -> requirements -> evaluation
        Front Readiness  |  ES&H Readiness G1-G5   (no compensation)
                              |
   State engine | Constraints | Evidence & audit | Measurement & value
                              |
  Field (offline) | Supervision | Management assurance | Integration ops

Bounded contexts

Work Package & CompositionApplicability & RequirementsFront ReadinessES&H Readiness (G1–G5)Work Control TransactionsDocument Authority & ChangeConstraints & AlertsAuthority, Delegation & IAMEvidence & Audit ReconstructionOffline, Sync & ConflictMeasurement & Value CaptureIntegration & ObservabilityConfiguration & TaxonomyAI Assistance (advisory)

State model

Three independent dimensions; never collapsed into one field.

Operational

READY · CONDITIONAL · HOLD · STOP

During execution

CONTINUE · REASSESS · HOLD · STOP

Document / transaction

DRAFT · REVIEW · APPROVED · RE-AUTHORIZED · SUPERSEDED · EXPIRED · CLOSED · CANCELLED

Technology

ONLINE · OFFLINE · SYNC_PENDING · CONFLICT · SOURCE_UNAVAILABLE

Valid combination: Permit APPROVED + Technology ONLINE + Operational HOLD, because client release is pending. HOLD prevents release or resumption; STOP requires active work to cease.

System-of-record assumptions

No second system of record is created silently.

Object class	Authoritative source	Integration mode
Controlled documents, procedures, PETS, standards	Aconex	Read / event
WBS, activities, schedule, look-ahead	Primavera P6	Read
Permits, JHA, isolation, Sanction to Test, work packs	Q4 / Entity Desk	Read / event
Fatal risks, critical controls, verification state	Forwood or equivalent	Read / event
Roster, competency, qualification validity	People & Training	Read
Operational fitness flag only	Health status service	Read, minimum exposure
System / subsystem completions state	Smart Completions / BCSTools	Read (contract open — ADR-06)
Integrated readiness decision, constraints, evidence lineage	This readiness layer	Owned

Architecture decision register

Open decisions are surfaced rather than silently resolved by the prototype.

ADR-01Q4 extension versus integrationOPEN

Context

Q4 / Entity Desk is a mature transactional work-control capability. The readiness layer needs its objects but must not duplicate them.

Options

Extend Q4 with readiness modules · Integrate read-only via adapter · Replace Q4

Consequences

Integration preserves transactional custody but depends on event-stream fidelity. Extension risks coupling readiness logic to a transactional release cycle.

Owner

Enterprise Architect

Evidence

Q4 object catalogue; adapter contract v3.1

ADR-02System of record for the Work Package transactionOPEN

Context

Work pack objects exist in Q4 and in completions; the readiness layer creates an integrated decision context over them.

Options

Q4 owns the work pack · Completions backbone owns it · Readiness layer owns a decision-context object referencing both

Consequences

A wrong choice creates a second silent system of record.

Owner

Enterprise Architect

Evidence

Current ID mapping across Q4 / P6 / Completions

ADR-03Authoritative restriction/constraint registerOPEN

Context

Constraints are raised today in project controls, ES&H and work control independently.

Options

Project controls constraint log · Readiness layer constraint register · Federated with originating-function ownership

Consequences

Federation preserves accountability but requires strict originating-cause vs detector separation.

Owner

Project Controls Manager

Evidence

Restriction taxonomy draft

ADR-04Authoritative competency sourceOPEN

Context

Roster, training and contractor competency data exist in multiple systems.

Options

Corporate training system · Contractor systems federated · Workforce master

Consequences

Affects whether an expired qualification is authoritative enough to drive HOLD.

Owner

Workforce Systems Owner

Evidence

PeopleAdapter contract v1.4

ADR-05Offline snapshot validity governanceOPEN

Context

Snapshots must be usable when a source is unavailable, without becoming a parallel truth.

Options

Fixed time window · Risk-based window by document class · Explicit governed re-verification event

Consequences

Arbitrary time limits are not invented by the prototype; validity is a configurable enterprise policy.

Owner

Document Control Manager

Evidence

Scenario 06 behaviour

ADR-06Integration backboneOPEN

Context

Smart Completions / BCSTools may already act as an enterprise integration backbone.

Options

Reuse completions backbone · Enterprise iPaaS · Direct point-to-point adapters

Consequences

Determines event fidelity, replay and operational support model.

Owner

Integration Architect

Evidence

CompletionsAdapter v0.9 draft contract

ADR-07Event architecture and replay guaranteesOPEN

Context

Offline reconciliation requires immutable, replayable events with base-version comparison.

Options

Event log with replay · Change data capture · Polling with version compare

Consequences

Directly determines whether Last-Write-Wins can be avoided under load.

Owner

Data Architect

Evidence

Sync model, Scenario 08

ADR-08Enterprise identity and device trust integrationOPEN

Context

Authority decisions require identity, attributes, device identity and session validity.

Options

Corporate IdP with ABAC claims · IdP plus local authority service · Local authority service only

Consequences

Affects separation of duties and offline authority evaluation.

Owner

Cybersecurity / IAM Architect

Evidence

Authority model attributes

ADR-09AI service placement, data residency and permitted useOPEN

Context

AI is optional and advisory; it must never approve, release or validate.

Options

No AI · Enterprise-hosted models · Vendor service with data residency controls

Consequences

Core deterministic functionality must remain fully available with AI disabled.

Owner

Enterprise Architect

Evidence

Scenario 12 proposal / rejection record

Technical review gates

Gate A — Process Integrity

The product models work preparation and release decisions, not a screen workflow. Every state is derived from source conditions.

Gate B — Authority Integrity

Decisions are attribute-based; technical access grants no operational authority; missing authority with no valid delegate yields HOLD.

Gate C — Information Integrity

Every critical item carries source system, object ID, revision and last-verified timestamp.

Gate D — Control Integrity

No aggregate score exists, so a legal or critical-control gap cannot be compensated. Answer: NO.

Gate E — Failure Integrity

Offline, stale source, missing approver and conflicting data each have explicit, safe behaviour.

Gate F — Enterprise Architecture Integrity

The layer adds integrated decision readiness; it does not duplicate document custody, scheduling, transactions or control assurance.

AI governance

AI is optional, advisory and fully separable. Core functionality is unaffected when disabled.

AI may

Extract controlled-document information
Summarize change and assess candidate materiality inputs
Suggest applicability and identify duplicate requirements
Identify cross-source inconsistency and propose relationship mappings
Assist semantic search and flag anomalies

AI must never

Create legal requirements
Approve or release work
Validate critical controls or authorize a permit
Remove a HOLD or authorize an exception
Replace a competent human decision