[christophersesugh]

Purpose

Move the MemoFS manifesto editorial work out of memofs#38 and into the repository that actually owns the published manifesto page.

The documentation app already serves /manifesto from content/manifesto/index.md. This replaces that existing document in place; it does not create a second manifesto under the product guides or change documentation routing.

Editorial revision

• Recast the long, implementation-heavy article as a public manifesto: the problem, a positive conviction, eight enduring commitments, and a clear invitation to challenge the work.
• State the core philosophy: inspectable canonical files; provenance and authorized correction; visible conflicts; honest freshness; local independence; open portability; evidence retention; and testable recovery.
• Remove unverifiable assertions about shipped SDKs, guaranteed trust, universal expiry multipliers, automatically reversible actions, cloud behavior, and perfect agent compliance.
• Distinguish the direction of the rebuild from features already available. Keep detailed guarantees, file schemas, and algorithms in the MemoFS ADR/specification work rather than in a manifesto.
• Preserve the existing author's attribution and original publication date.

Writing references

The revision was informed by the concise values-plus-principles pattern of the Agile Manifesto, the Centre for the Just City's manifesto-writing guidance (state values, name the problem, give a constructive direction, end with action), and Humanizer's public editorial guidance (remove inflated claims, formulaic contrasts, filler, and uniform rhythm). The humanizer skill was not available as an installed runtime skill, so its public writing guidance was reviewed and applied directly.

Verification

• Confirmed that src/routes/manifesto.tsx reads content/manifesto/index.md through the existing configured manifesto docs collection.
• Validated frontmatter, a single H1, non-empty sections, final newline, and no trailing whitespace.
• Confirmed that the branch changes only one file, with no package, route, deployment, or dependency changes.
• Documentation CI checks on this new PR (not yet available at creation).

Release boundary

Review and merge in the documentation repository, not MemoFS. A merge alone does not deploy documentation; staging/production publication follows the documentation repository's separate release workflow. This PR changes no MemoFS runtime behavior and does not imply that any of the proposed rebuild capabilities are already implemented.

Supersedes memofs#38, including the maintainer's relocation and editorial comment.

[christophersesugh]

The editorial rewrite has now been incorporated directly into the 0xBUFF site route in platform#106, with the original author and date preserved. The documentation-specific cleanup, footer link and permanent redirect are in documentation#14.

Per the revised publishing decision, the canonical manifesto will be https://0xbuff.com/products/memofs/manifesto, not a document served by docs.0xbuff.com. Closing this PR as superseded without merging. Release platform#106 before documentation#14 to avoid a temporary broken redirect.