540 · cultural programming platform

Rumaia

cultural programming, shaped around connected services, live status and coordinated ownership.

Rumaia is a fictional cultural programming platform organisation created as Interlink Apps catalogue design 540. The page architecture translates the organisation's real operating unit — the programme cycle — into navigation, evidence, case work, people, questions and conversion rather than relying on decorative hero content alone.

Rumaia visual study
Framed dossier theatre · modular evidence blocks · high-contrast monochrome · staggered sectional revealprogramme cycle

01 / Offer

Built around the work, not a generic template.

01

cultural programming discovery and strategy

Delivered through a named programme cycle with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every programme cycle.

02

platform implementation and operations

Delivered through a named programme cycle with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every programme cycle.

03

Governance, exception handling and stakeholder coordination

Delivered through a named programme cycle with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every programme cycle.

04

Evidence, reporting and continuous improvement

Delivered through a named programme cycle with scope, named owner, constraints, decisions, measures, exceptions and accepted close-out for every programme cycle.

02 / Method

1

Frame · define purpose, boundaries, risks and ownership

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

2

Map · translate the operating system into a visible service model

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

3

Deliver · execute through explicit checks, decisions 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

Rumaia programme 540-A

A representative cultural programming engagement organised one programme cycle around a clear brief, accountable roles and evidence that could survive handover.

Case 2

Rumaia operating cycle 540-B

The team tested the platform model under live constraints, recorded exceptions and translated every unresolved issue into a named next action.

Case 3

Evidence release 540-C

A recurring review converted activity into a concise decision record showing outcomes, trade-offs, ownership and what the organisation would change next.

04 / Evidence

99%work items closed with explicit evidence
2dtypical decision-to-owner handover
27representative operating records reviewed
0anonymous claims presented as proof

05 / People

Thandi Naidoo

Practice lead

Noah Patel

Delivery lead

Zuri Ndlovu

Evidence lead

06 / Notes

Note 01

What credible evidence looks like in cultural programming

Note 02

Why programme cycle ownership improves service quality

Note 03

Designing platform systems around exceptions rather than ideal cases

07 / Questions

Is this a real organisation?

No. Rumaia is a fictional Interlink Apps identity demonstrating a production-grade website for cultural programming platform.

How is delivery made measurable?

Every programme cycle carries scope, ownership, constraints, decisions, acceptance criteria and close-out evidence from the beginning.

Can this design adapt to another organisation?

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