AssetsCompliance v1.1 — Current Demo

What Changed From v1.0

v1.1 kept v1.0's connected data model — obligations, controls, ownership, evidence, actions, reporting, and integrations — but changed how a practitioner arrives at and reasons about that data.

Every workspace now starts empty by design. A practitioner mounts a simulated compliance data source before any obligation, control, or evidence record appears, and can unmount it again. Workspace identity and "Open Work" are derived from whichever sources are currently mounted, not assumed in advance.

v1.1 also replaced v1.0's single generic control view with three independently reasoned Control Positions, and replaced v1.0's four separately named review journeys with one redesigned seven-step validation journey that opens with mounting compliance data.

Demo Narrative

The v1.1 demo narrative starts from an empty workspace, walks through mounting a simulated data source, and then follows the practitioner through establishing the three Control Positions, investigating a material Exposure, evaluating remediation and reassessment, testing Intelligence as decision support, and defending the professional report.

Empty-By-Design Behaviour, Data Mounting, And Workspace Scoping

"Empty by design" means a v1.1 workspace shows no obligations, controls, ownership, evidence, actions, or reports until the practitioner deliberately mounts a data source. This is a review-journey choice, not a defect: it lets a practitioner see exactly how much of the control picture depends on what has actually been connected.

Mounting a source is a simulated ingestion journey: selecting a source type, walking through a deterministic mock dataset, reviewing a data-readiness and mapping assessment, and then mounting the result into the workspace's live records. Unmounting reverses this. Workspace identity, and every downstream view, is scoped to whatever sources are currently mounted for that workspace.

Open Work, Data Readiness, And Workspace Health

"Open Work" is the practitioner's workspace-scoped worklist, derived from currently mounted data rather than a fixed checklist. "Data Readiness" assesses, capability by capability, how ready the mounted data is to support obligation mapping, control coverage, evidence confidence, execution assessment, each Control Position, exposure analysis, and reporting — each rated Ready, Limited, Partial, or Not established with a plain-language reason. "Workspace Health" gives a workspace-level view of that same readiness.

Regulator, Organisation, And Practitioner Control Positions

"Control Position" is v1.1's central concept, and it is deliberately three independent positions rather than one: the Organisation's actual operational control state; the Practitioner's independent professional judgement, with rationale, confidence, and evidence reliance; and the Regulator's position, assessed against applicable regulatory obligations and expectations.

These three positions can agree, partially agree, or diverge. v1.1 treats divergence as meaningful information about the control picture, not as an error to resolve away — a deliberate product decision carried through Control Picture, Exposure, and the professional report.

Control And Evidence Assessment

Control assessment in v1.1 is frequency-aware: whether a control executed at the frequency its design requires, not only whether it exists on paper.

Evidence assessment adds an explicit quality basis to each evidence record: sufficiency, relevance, reliability, a qualitative confidence rating, and any recorded conflict with other evidence. This basis is visible directly on the evidence record, not only inferred from downstream readiness or intelligence flags.

Exposure, Intelligence, And Traceability

"Exposure" in v1.1 is explainable: each material exposure carries a structured cause, a priority basis, and a traceability chain back through the obligation, control, execution, and evidence that produced it, using live, working links rather than placeholder routes.

"Practitioner Intelligence" surfaces and prioritises these exposures without an opaque score — its trigger, significance, and required action are stated in plain language, and every traceability link either opens the real underlying record or is shown as non-actionable text rather than a broken link.

Reporting And Review Workflow

v1.1's professional report presents all three Control Positions together with their divergence, connected evidence, exposure, remediation effectiveness, reassessment history, and change over time, in a form intended to be usable directly in a client, management, board, or regulatory conversation.

Reporting distinguishes what AssetsCompliance can generate right now from the current mounted workspace state from any separate mounted report-record catalogue, so availability is always derived from real data rather than assumed.

The Owned, Evidenced, Exposed, Reportable Model

Underneath Control Picture, v1.1 continues to explain control status through four dimensions rather than a single pass/fail flag: whether a control is Owned, Evidenced, Exposed, and Reportable. Each dimension is explainable in its own right rather than collapsed into one generic status.