336 · cyber assurance delivery

Vector Works

cyber assurance, organised around field execution and measured close-out.

Vector Works is a fictional cyber assurance delivery organisation created as catalogue design 336. Its interface treats control records, responsibilities, constraints and evidence as the visual system, giving clients a credible long-form website rather than a decorative landing page.

Vector Works visual study

Human-centred service pathway

01 / Offer

Built around the work, not a generic template.

01

cyber assurance discovery and planning

Delivered through a named control record with scope, named owner, constraint, decision record, performance measure and accepted close-out for every control record.

02

delivery implementation

Delivered through a named control record with scope, named owner, constraint, decision record, performance measure and accepted close-out for every control record.

03

Operational governance and exception handling

Delivered through a named control record with scope, named owner, constraint, decision record, performance measure and accepted close-out for every control record.

04

Evidence, reporting and continuous improvement

Delivered through a named control record with scope, named owner, constraint, decision record, performance measure and accepted close-out for every control record.

02 / Method

1

Frame · establish purpose, constraints and ownership

Each stage leaves an explicit decision trail before the next stage begins.

2

Model · translate the operating system into a visible plan

Each stage leaves an explicit decision trail before the next stage begins.

3

Deliver · run the work with explicit checks and handovers

Each stage leaves an explicit decision trail before the next stage begins.

4

Prove · close with evidence, unresolved risks and next actions

Each stage leaves an explicit decision trail before the next stage begins.

03 / Work

Representative engagements

Case 1

Vector programme 336-A

A representative cyber assurance engagement aligned stakeholders around one control record, a documented decision trail and measurable acceptance criteria.

Case 2

Works field cycle 336-B

The team tested the delivery model under live operating constraints, recorded exceptions and handed every remaining action to a named owner.

Case 3

Evidence release 336-C

A recurring review turned activity into a compact public-facing account of outcomes, limitations, lessons and the next accountable move.

04 / Evidence

4visible delivery gates
100%critical actions assigned to named owners
1evidence record per completed control record
0anonymous performance claims

05 / People

Jonah Naidoo

Practice lead

Priya Botha

Delivery lead

Sofia Mokoena

Evidence lead

06 / Notes

Note 01

What credible evidence looks like in cyber assurance

Note 02

Why control record ownership improves handover quality

Note 03

Designing delivery systems around real exceptions

07 / Questions

Is this a real organisation?

No. Vector Works is a fictional Interlink Apps identity demonstrating a production-grade website for cyber assurance delivery.

How is delivery made measurable?

Each control record carries scope, ownership, acceptance criteria, decisions and close-out evidence from the beginning.

Can this identity adapt to another organisation?

Yes. Content, imagery and operating terminology can change while retaining the responsive, accessible information architecture.