AssetsCompliance v1.0 — Foundation

Release Purpose And Problem Addressed

v1.0 was built to answer a structural problem rather than a single feature request: compliance leaders in fragmented organisations can usually point to individual controls, but struggle to show how obligations, ownership, evidence, actions, and reporting connect into one defensible view.

The release replaced an earlier product scaffold with a coherent demo foundation, so a reviewer could move from a dashboard, through obligations and controls, into evidence and actions, and out to reporting and integrations, without leaving a single connected model.

Demo Narrative And Connected Control Model

The v1.0 demo narrative followed a dashboard-first structure: a headline control position, a connected review chain, and current exposure, before moving into the obligation-to-control-to-evidence-to-action chain for a representative case.

Obligations, controls, ownership, evidence, actions, and reporting were modelled as connected records rather than separate lists. An interactive Control Picture let a reviewer inspect a single obligation or control and see how ownership, evidence, and reportability connected to it. Senior Oversight Reporting summarised that same picture for an executive audience.

Integrations were represented as lineage and a connector universe: source health, freshness, and source-to-record relationships, rather than as a replacement for the underlying systems of record.

A first compliance-intelligence layer surfaced findings drawn from this connected model, giving the demo a route from raw obligations and evidence to prioritised, explainable matters.

Role Of Compliance Intelligence

In v1.0, compliance intelligence sat downstream of the connected obligations, controls, evidence, and actions model: it surfaced findings and priority matters derived from that data, feeding into Senior Oversight Reporting rather than standing as an independent decision layer.

What v1.0 Established

v1.0 established the connected data model — obligations, controls, ownership, evidence, actions, reporting, and integrations as one traceable structure — and a practitioner review discipline for validating it: four separately named review journeys (Senior Oversight Review, Control Workflow Review, Evidence and Reporting Review, and Integration and Lineage Review), each aimed at a different reviewer role.

It also established the surrounding review-access infrastructure that later releases continued to build on: demo accounts, application-wide notifications, and Stripe-backed instant-unlock and checkout flows for reviewer access.

Relationship To v1.1

v1.0 presented control primarily through a single generic view and started every workspace from a fixed, already-populated demo dataset. v1.1 kept the same connected data model but rebuilt the review experience around three independently reasoned Control Positions and a workspace that starts empty until the practitioner mounts data into it.

Nothing in this document attributes v1.1's Control Position model, data-mounting behaviour, or evidence-quality judgements to v1.0 — those capabilities were introduced in v1.1, described in its own release documentation.