Manifest Example

The following is a complete, well-formed *.manifest.mdoc file. It illustrates the relationship between values, principles, goals, and NFRs, and shows how manifest content is referenced from other documents.

type: manifest
id: product
title: Product Manifest
status: ready
tags: [core, identity]
context: []


{% manifest scope="public agent" %}

{% tldr %}
The foundational values, principles, and goals for the bookmarking application.
Design decisions and implementation rules trace back to this document.
{% /tldr %}

{% value id="SIMPLICITY" label="Radical Simplicity" %}
Every interaction should have the least possible friction. If a feature requires
explanation, it should be redesigned. We will sacrifice capability before we
sacrifice clarity.
{% /value %}

{% value id="OWNERSHIP" label="User Ownership" %}
The user's data belongs to the user. We will never lock it in, monetise it,
or expose it without explicit consent.
{% /value %}

{% principle id="LOCAL_FIRST" label="Local-First Storage" %}
Data is stored on the user's device first. Cloud sync is an enhancement,
not a prerequisite. The app must be fully functional offline.
{% /principle %}

{% principle id="NO_MAGIC" label="No Hidden State" %}
The application must not perform actions the user did not initiate.
Background sync, auto-tagging, and AI suggestions must be opt-in and
clearly signalled in the UI.
{% /principle %}

{% goal id="G1" label="Core Bookmarking Loop" status="achieved" %}
A user can save, browse, and open a bookmark within three interactions.
Success metric: task completion rate > 95% in usability testing.
{% /goal %}

{% goal id="G2" label="Offline Reliability" status="pending" %}
The app functions fully without a network connection for all read and write
operations. Success metric: zero data-loss reports in 30-day offline test.
{% /goal %}

{% requirement id="perf" priority="must" tags="performance" %}
All read operations must complete within 200ms on a mid-range mobile device.
{% /requirement %}

{% requirement id="a11y" priority="must" tags="accessibility" %}
All interactive elements must meet WCAG 2.1 AA contrast and focus requirements.
{% /requirement %}

{% requirement id="privacy" priority="must" tags="security privacy" %}
No user data is transmitted to external services without explicit opt-in.
{% /requirement %}

{% /manifest %}

How manifest content is referenced from other documents

From a design rule:

{% rule id="no-external-sync" force="must" ref="manifest/product#privacy" %}
No component may send bookmark data to a third-party service.
{% /rule %}

From a feature’s context:

context:
  - manifest/product

This inlines the manifest TLDR into the feature’s agent bundle, giving the agent the project’s values when reasoning about requirements.

What makes this example good

Values explain the why: Each value states not just what is valued but what trade-off it implies.
Principles are actionable: Each principle translates a value into a concrete decision rule.
Goals are measurable: Each goal names an observable success state, not a vague aspiration.
NFRs are specific and tagged: priority="must" and tags (performance, accessibility) allow filtering in the agent bundle.
One manifest per concern: This manifest covers product identity. A separate manifest would cover API design principles or security posture — not mixed in here.