Phase 1.2 — All the lists of things

Bryan's handoff doc (pasted 2026-08-13). The source of truth for taxonomies, acts, events, places, relationships, proof types, the comment object, and the recognition economy. lib/scoring.ts implements §Gamification; the seeded lookup tables implement the taxonomies.

Purpose

This document organizes the working lists and naming structure discussed for Phase 1.2 into a cleaner stakeholder format. It is intended to show the product as a structured two-sided marketplace between Seekers and Helpers, and to make the list system readable enough for review before it becomes implementation work.

The goal is to define the major categories, formal names, and reusable objects that the product needs in order to support requests, offers, completions, proof, comments, place catalogs, and recognition in a consistent way.

Product model

The product is a mobile-first, two-sided marketplace for acts of faith and mercy. A Seeker asks for help for a person, event, and place, and a Helper completes a specific act, optionally with proof, comments, and shareable reassurance.

The product needs these major objects and dimensions:

• Seeker
• Helper
• Person
• Relationship to the Seeker
• Event
• Place
• Act
• Mission or Request
• Helper Offer
• Proof of completion
• Comment object
• Recognition and scoring

Helper offer language

The helper side should use explicit marketplace language, not just generic request flows.

Core helper-offer pattern:

I am headed to [PLACE]; who wants [ACT] while I am there?

Examples:

• "I am headed to St. Peter's Basilica; who wants a candle lit while I am there?"
• "I am going to the hospital chapel; who wants me to say a prayer for someone while I am there?"
• "I am climbing Croagh Patrick; who wants me to carry an intention up the mountain?"
• "I am going to Mass at St. Mary's; who wants an intention carried with me?"

Acts

Acts are the core marketplace inventory. They are the things a Seeker asks for, the things a Helper offers, and the units that drive matching, completion, proof, and recognition.

Core prayer acts

• Short prayer
• Prayer at a set moment
• Prayer on behalf of another person
• Prayer for a parish member or community
• Prayer for a world event
• Decade of the Rosary
• Full Rosary
• Novena start
• Novena continuation, day X of Y
• Chaplet or mercy prayer
• Join-at-time group prayer
• Pray-at-noon collective act
• Mass attendance with intention carried
• Eucharistic adoration hour

Place-bound devotional acts

• Light a candle
• Light a candle at a named church
• Visit a shrine
• Visit a grotto
• Visit a chapel
• Visit a hospital chapel and pray
• Visit a gravesite
• Tidy or tend a gravesite
• Visit a memorial statue or sacred monument
• Pray outside a hospital
• Pray outside a stadium or event gate
• Pray at a cathedral for peace or wisdom
• Pray at an airport or gate before travel

Pilgrimage and movement acts

• Pilgrimage walk
• Rosary walk
• Prayer walk
• Climb a holy mountain
• Carry an intention during a route, hike, or walk
• Multi-day devotion route

Support and companion acts

• Leave a note of encouragement
• Leave a written blessing or reflection
• Invite others to join in prayer
• Broadcast a shareable link or QR invitation

Proof and digital companion acts

• Upload candle photo
• Upload church photo
• Upload shrine or grotto photo
• Upload gravesite photo
• Upload pilgrimage or climb photo
• Send written reflection
• Generate digital saint card
• Generate prayer card or certificate
• Share mission summary link

Events

Events are the reasons support is needed. They help organize missions, shape feed categories, and make the product useful for both personal moments and world-layer prayer moments.

Health and medical events

• Surgery
• Medical procedure
• Chemotherapy or chemo day
• Radiation treatment
• MRI, scan, or diagnostics
• Hospital admission
• Emergency or trauma
• ER visit
• Recovery after surgery
• Chronic illness flare
• Mental health crisis
• Addiction recovery milestone
• Hospice transition
• End-of-life vigil

Travel and safety events

• Flight departure
• Flight arrival
• Long drive or road trip
• International travel
• Pilgrimage departure
• Mission trip departure
• Safe return home
• Travel delay or disruption

Education and testing events

• Final exam
• First day of school
• College exam
• Bar exam
• Licensing exam
• Admissions test
• Interview day
• Graduation

Family and sacramental events

• Wedding anniversary
• Sacramental anniversary
• Birthday
• Death anniversary
• Funeral day
• Birth or newborn arrival
• Reunion
• Reconciliation or difficult family conversation

Work and life-transition events

• Job interview
• Starting a new job
• Retirement
• Moving house
• Business launch
• Financial hardship
• Difficult decision
• Career transition

Sports, civic, and world events

• Big game or championship
• Election day
• Community tragedy
• Public tragedy, such as wildfire, flood, or shooting
• Peace and unity moment for a city, state, or nation
• Timed parish-wide or city-wide prayer moment

Liturgical and devotional events

• Novena day X of Y
• Mass offering date
• Eucharistic adoration hour
• Rosary day
• Feast day
• Holy day of obligation
• Christmas
• Easter
• All Souls Day
• Divine Mercy Sunday
• Lent or daily Lent act

Places

The place system should support both generic place types and formal named place catalogs. A small town can have a short list of local churches and chapels, while Rome or Lourdes can have a richer list of formal pilgrimage destinations.

Sacred and devotional place types

• Parish church
• Cathedral
• Basilica
• Shrine
• Grotto
• Chapel
• Hospital chapel
• Adoration chapel
• Monastery or convent chapel
• Pilgrimage site
• Holy mountain or pilgrimage climb route
• Cemetery chapel
• Gravesite or family plot

Care, crisis, and service place types

• Hospital
• Emergency room or ER
• Surgery center
• Cancer treatment center
• Rehabilitation center
• Hospice
• Nursing home or senior care facility
• Shelter
• Disaster zone
• Funeral home
• Cemetery
• Prison
• Jail
• Military base

Travel, education, and public place types

• Airport
• Terminal or gate
• Train station
• School campus
• Parish school
• College chapel
• Test center
• Stadium
• Arena
• Courthouse
• City hall
• Polling place

Geographic abstractions

• Near me
• Near the requester
• Near the recipient
• Near a parish
• Any Catholic church within X miles
• Within a city
• Within a region
• National
• Global or world layer

City and regional place catalogs

A local town catalog may include only a few formal places, such as three parish churches, one hospital chapel, one cemetery, and one shrine.

A major Catholic city or pilgrimage destination can include basilicas, cathedrals, shrines, relic sites, named pilgrimage routes, and historically important devotional locations.

This creates two useful layers:

• Generic place types for broad matching
• Formal place catalogs for locally meaningful offers and requests

Important Catholic places, walks, and journeys

These should be treated as formal named places and formal named routes rather than generic place types.

Major basilicas and cities

• St. Peter's Basilica, Vatican City
• Archbasilica of Saint John Lateran, Rome
• Basilica of Saint Paul Outside the Walls, Rome
• Basilica of Saint Mary Major, Rome
• Basilica of St. Francis of Assisi, Assisi, Italy

Major shrines and holy sites

• Sanctuary of Our Lady of Lourdes, Lourdes, France
• Shrine of Our Lady of Fátima, Fátima, Portugal
• Basilica of Our Lady of Guadalupe, Mexico City, Mexico
• Shrine of Our Lady of Knock, Knock, Ireland
• National Shrine of Our Lady of Champion, Champion, Wisconsin
• El Santuario de Chimayó, Chimayó, New Mexico

Named pilgrimage walks and journeys

• Camino de Santiago / Way of St. James
• St. Olav Way / St. Olavsleden
• Walk to Mary, Wisconsin
• Way of St. Joseph, Indiana
• Camino of Maryland
• El Camino de Chimayó, New Mexico

Relationship to the Seeker

This relationship layer makes requests more human and provides structured context for filtering, matching, analytics, and recognition.

Immediate family

• Self
• Spouse
• Father
• Mother
• Grandfather
• Grandmother
• Son
• Daughter
• Brother
• Sister

Extended family and social ties

• Uncle
• Aunt
• Cousin
• Nephew
• Niece
• Close friend
• Friend
• Neighbor
• Mentor
• Parish friend

Care, service, and public roles

• Parish member
• Pastor
• Priest
• Soldier
• Veteran
• First responder
• Nurse
• Doctor
• Patient
• Prisoner
• Person in jail

Proof of completion

Proof builds trust, reassurance, and shareability.

• Trust-based completion
• Two-tap completion
• SMS YES completion
• Timer auto-complete
• Written note
• Reflection or blessing
• Photo proof
• Story card auto-generated
• Shareable prayer card or certificate

Comment object

Commenting should be treated as a reusable object that can attach to an act, event, mission, helper offer, proof item, story card, parish broadcast, or world-layer event.

Comment object fields

• comment_id
• parent_object_type
• parent_object_id
• parent_comment_id for replies
• author_user_id
• author_role
• comment_type
• body_text
• visibility_scope
• created_at
• edited_at
• status
• moderation_reason
• report_count

Comment object uses

• Encouragement comment
• Prayer note
• Status update
• Completion reflection
• Witness or testimony
• Reply to another comment
• Moderator note

Gamification and recognition

The scoring layer should go beyond a simple streak and define what actions earn points, what completions earn bonuses, and what patterns warrant badges.

Point-worthy actions

• Short prayer completed
• Candle lit
• Rosary completed
• Novena day completed
• Mass attended with intention carried
• Eucharistic adoration hour
• Shrine, chapel, hospital chapel, or cathedral visit
• Gravesite visit or tending
• Pilgrimage walk or climb
• Encouragement note or reflection
• Helper offer accepted and fulfilled

Bonus and multiplier examples

• Standard completion confirmation: base completion bonus
• Completed with written reflection: extra completion bonus
• Completed with image proof: large completion bonus
• Completed with image and note: larger completion bonus
• Completion with accepted proof object: 2x points
• Completion with altar-level or special-location proof: 2x points
• Completion with image as proof: +1000 bonus points
• Completion with image and reflection: +1500 bonus points
• Multi-day streak continuation: 1.25x or 1.5x multiplier

Badge-worthy behavior

• Pilgrim
• Candle Bearer
• Rosary Keeper
• Novena Companion
• Hospital Intercessor
• Travel Guardian
• Grave Tender
• Parish Helper
• Mercy Witness
• World Watcher
• Mission Champion

Suggested prefix system

• REL- = relationship codes
• PLC- = place codes
• EVT- = event codes
• ACT- = act codes
• PROOF- = proof codes
• CMT- = comment codes
• BADGE- = badge codes

Recommended Phase 1.2 starter subset

• Core acts: prayer, candle, Rosary, novena, Mass intention carried, chapel visit, grave visit, encouragement note
• Core events: surgery, chemo, flight, exam, first day of school, wedding anniversary, death anniversary, job interview, moving house, world event
• Core places: parish church, cathedral, shrine, grotto, hospital chapel, cemetery, gravesite, airport, school, test center, stadium, prison, military base, near me
• Core formal places: St. Peter's Basilica, Lourdes, Fátima, Guadalupe, Knock, Assisi, Camino de Santiago
• Core proof: completion tap, written note, image proof
• Core recognition: day streak, points, image bonus, category badge