Inventory model

    One shared language for status, visibility, and next move.

    • Status: Live, Server-configured, Local build, Doc-backed concept, Sensitive/private, Internal, Placeholder.
    • Visibility: Public hub, Public spoke, Private annex, Internal only.
    • Artifact: Live site, Codebase, Microsite, WordPress package, Deck/doc, Research archive.
    • Next move: Keep live, Launch next, Package first, Verify, Archive, Hold private.

    Keep and clarify

    Tier 1 lanes already shaping the public ecosystem.

    • faithcheltenham.com stays the main public hub and routing layer.
    • motheratwater.com stays live while the larger expansion gets packaged.
    • THEFAYTH.net stays the memory-board and archive lane, but should be freshly re-verified before publishing new live badges.
    Open faithcheltenham.com Open motheratwater.com

    Launch next

    The strongest outward-facing local builds.

    • The Children's Internet: presentation-ready microsite with clear deploy path.
    • Leaps of Faith: manuscript-driven poetry app with narration support.
    • ThankFish: web-first translation MVP with demo mode and plan docs.
    • AI Screenwriting / Story Arena: public prototype lane for screenwriting and submissions.
    • Hydrogel World: the cleanest public-facing hydrogel narrative currently in the workspace.

    Package first

    Substantial lanes that still need a tighter front door.

    • Diverse Data Centers: real investor MVP codebase, but still needs stronger outward framing.
    • Global Team Ops: solid WordPress-first operations stack that should be packaged for partner or internal rollout first.
    • Black2Africa: packaged public hub, but deployment access was blocked.
    • XXYYZZ Society: real umbrella identity with bridge-page material, but not yet a polished standalone site.
    • Atwater Creative and DOY remain better as packaged narratives than immediate public drops.

    Kept separate

    Sensitive and private lanes are not part of this public roadmap.

    Adult-adjacent, creator-platform, intimacy, and legally sensitive work is tracked in a separate private annex on purpose. The public roadmap stays public-safe by default.

    • Creator-platform families stay out of the main project grid.
    • Legally sensitive and survivor-adjacent lanes are packaged cautiously.
    • Internal utilities and empty placeholders do not get public status claims.

    Research backlog

    Google Keep export stays out of naming and scoping for now.

    Google Keep_XPATENTS.pdf is being treated as a backlog research artifact, not a canonical idea source.

    • It is a 40-page Chrome-generated export from April 8, 2026 UTC.
    • It contains heavy Google wrapper content and only a small set of non-Google links.
    • It should be OCR'd or otherwise curated before any project naming or product decisions rely on it.

    Canonical inventory

    The full local source of truth lives outside the public site root.

    The working inventory is maintained in local project documentation so the public roadmap can stay clean while private annex and internal backlog lanes remain separate.

    Back to projects