Manifold Grace
Design notebook · Grace Rosemary Nettey

App design ideas.

A growing collection of app concepts, interface studies and possible user journeys. Explore each idea through its mock-up.

Design concepts · Controls illustrate the proposed experience using no real profiles or personal records.

3 ideas

Distinct Histories

Distinct Histories: DH centred in a gold sun above separate teal and gold paths. Distinct histories. Shared values. Equal partnership.
Distinct histories. Shared values. Equal partnership.

A genealogy-qualified introduction app centred on shared faith, formation, heritage and purpose. Applicants submit their genealogical background for review. Once approved, they can swipe through eligible profiles automatically aligned with their presets and chosen lineage interests. The proposal welcomes applicants from any background who meet the same documentation and consent requirements.

Family networksShared purposeConsent-led introductions

Core design

  • Map maternal and paternal branches with sources, attributed oral history and visible gaps.
  • Distinguish biological, adoptive and marital relationships; record historical offices separately from present authority.
  • Block marriage matches within prohibited kinship boundaries before profiles enter the swipe queue. Apply legal prohibitions and the stricter boundary selected by either person; preferences cannot override these blocks. Hold uncertain or incomplete comparisons for review.
  • Explore faith, service, stewardship and aspirations alongside each person’s demonstrated conduct.
  • Qualify applicants through review of sourced genealogical submissions, with a correction and resubmission route. Keep private evidence separate from the profile, and share living relatives’ records only with permission. Clinical genetic advice remains separate.
Design decisions & next questions

Admission depends on adequate genealogical evidence and consent, not a title or prominence. Review standards must recognise different record traditions, including attributed oral histories and archival gaps. Approval to use the app is separate from clearance of a particular match. An unresolved kinship comparison stays on hold; documentation cannot certify the absence of every distant shared ancestor. Titles and ancestry would not be character scores.

Explore an introduction

Interface mock-up · explore admission, presets and the eligibility gate.

The sample assessment is manually selected to illustrate the gate. No real admission, ancestry check, profile matching or swiping service operates here.

Intentional dating

A separate dating concept with more precise filters for intentions, values, readiness and everyday compatibility. Family-tree documentation is not required.

Clear intentionsStricter filtersMutual choice

Core design

  • Separate firm requirements from preferences and topics for discussion.
  • Filter relationship intentions, faith, children, location and lifestyle.
  • Show what is self-described and what has actually been verified.
  • Support thoughtful introductions, with attraction and communication explored by mutual choice.
  • Provide reporting, blocking, identity checks and controls over contact sharing.
Design decisions & next questions

Which filters should be firm? How should changed preferences be handled? What would meaningful identity verification involve? Filter choices should be transparent; personal worth would not be ranked.

Your introduction brief

Interface mock-up · no profiles or matches.

Agency.ai · AI agent workspace

An app workspace extending the AI agent website idea: clients describe a task, select a workflow, review proposed actions and track progress through a dashboard.

Client dashboardAgent workflowsHuman approval

Core design

  • A service catalogue covering research, administration, support and digital operations.
  • Client sign-in and two-factor authentication as proposed account features.
  • Task briefs, progress, deliverables and activity records in one workspace.
  • Explicit permission before external actions, with appropriate access to connected services.
  • Human review, clear scope and agreed pricing before workflow activation.

View the existing Agency.ai website ↗ · Manifold Grace service context

Design decisions & next questions

Which workflows should be offered first? What access does each need? Where must a client approve an action? This mock-up does not connect accounts or run agents.

Plan an agent workflow

    Select a workflow to explore its proposed stages.

    A growing design notebook

    Each new entry can follow the same structure: the need, intended users, key features, an interactive mock-up and questions for the next design iteration.

    First three concepts recorded 17 October 2026.