ICOS / LCOS
Civic Commons Initiative
Service Requirement Documents (SRDs), Landing Page PRDs, and AI Build Prompts
Overview
This document contains:
- High-level Service Requirement Documents (SRDs)
- Landing Page Product Requirement Documents (PRDs)
- Shared Information Architecture
- Shared UX / Brand Guidelines
- Claude/Codex implementation prompts designed to work within an existing architecture/codebase
The goal is not merely to create events. The goal is to create:
- recurring civic rituals
- social infrastructure
- participatory public culture
- ecological stewardship systems
- commons-oriented local governance
- embodied forms of belonging
The system should feel:
- warm
- human
- ecological
- participatory
- grounded
- non-corporate
- timeless
Avoid:
- startup/SaaS aesthetics
- over-commercialization
- excessive gamification
- political tribalism
- over-optimization
Shared Site Information Architecture
Top-Level Navigation
- Home
- Vision
- Commons Patterns
- Start Locally
- Stories
- Governance
- About
Shared Design Language
Visual Tone
Inspired by:
- field journals
- ecological atlases
- civic handbooks
- landscape architecture publications
- modern monastery aesthetics
- tactile/public materials
UX Principles
- calm spacing
- readable typography
- warm neutrals
- minimal animation
- soft transitions
- image-forward storytelling
- participatory calls-to-action
- low cognitive load
Emotional Goals
Users should feel:
- welcomed
- grounded
- hopeful
- useful
- capable of participating
- less alone
Shared CTA Patterns
Use language that implies participation instead of consumption.
Preferred:
- Start a Commons Circle
- Host a Gathering
- Bring This to Your Town
- Become a Steward
- Start Locally
- Learn the Pattern
- Join the Ritual
- Contribute a Story
Avoid:
- Sign Up
- Buy Now
- Join Our Platform
- Optimize Your Community
1. THE GREAT FEAST
Service Requirement Document (SRD)
Service Name
The Great Feast
Service Category
Civic Ritual / Food Commons / Social Infrastructure
Vision
Create recurring municipally or community-supported communal meals that strengthen civic identity, social cohesion, and local ecological economies.
Core Human Needs Addressed
- belonging
- nourishment
- ritual participation
- intergenerational connection
- civic identity
- reciprocity
Problem Statement
Modern cities increasingly lack:
- communal rituals
- interclass gathering spaces
- shared symbolic experiences
- connection to local food systems
Food has become individualized and commercialized rather than civic.
Primary Stakeholders
- residents
- chefs
- bakers
- farmers
- schools
- municipalities
- artists
- local nonprofits
Service Model
Recurring communal meal hosted in:
- parks
- streets
- plazas
- public commons
Supported through:
- local volunteers
- municipal grants
- local food partnerships
- community stewardship
Ritual Layer
- recurring cadence
- seasonal menus
- shared seating
- collective cleanup
- local storytelling/music
Participation Model
Residents can:
- cook
- volunteer
- donate ingredients
- host tables
- perform music
- facilitate cleanup
- document stories
Operational Requirements
- permits
- food safety coordination
- sanitation
- waste management
- accessibility planning
- multilingual signage
- volunteer coordination
Success Metrics
Quantitative:
- attendance
- repeat participation
- volunteer retention
- local food sourcing
Qualitative:
- perceived belonging
- civic pride
- emotional resonance
- cross-demographic interaction
Failure Modes
- commercialization
- over-branding
- excessive vendorization
- political capture
- exclusivity
Landing Page PRD
Goal
Inspire users to:
- emotionally connect with the vision
- understand the ritual pattern
- start local versions
- join stewardship efforts
Primary CTA
Start a Feast
Secondary CTA
Download the Feast Playbook
Hero Section
Headline: “A city that eats together remembers it belongs to itself.”
Subheadline: “The Great Feast is a recurring communal meal designed to rebuild civic belonging through food, ritual, and participation.”
Primary CTA Button: Start Locally
Secondary CTA: Learn the Pattern
Page Sections
1. Why It Matters
Discuss:
- loneliness
- fragmentation
- loss of civic ritual
- local food disconnection
2. What Happens At A Feast
- shared meals
- long tables
- local chefs/farmers
- music/storytelling
- cleanup rituals
3. The Pattern
Show:
- recurring cadence
- low barrier to entry
- local adaptation
- community stewardship
4. Start One Locally
Simple starter flow:
- Gather 5 people
- Pick a recurring date
- Use a public space
- Invite neighbors
- Share responsibility
5. Stories From Communities
Visual storytelling/photos/quotes.
6. Final CTA
“Bring The Great Feast To Your Town”
2. THE GREAT REPAIR
Service Requirement Document (SRD)
Vision
Restore repair culture, practical stewardship, and intergenerational skill sharing through recurring public repair gatherings.
Human Needs Addressed
- competence
- usefulness
- stewardship
- mentorship
- ecological responsibility
Problem
Modern systems incentivize:
- disposal
- isolation of expertise
- planned obsolescence
- consumer dependency
Service Components
- bike repair
- electronics repair
- textiles
- woodworking
- sharpening
- teaching stations
Participation Model
Residents:
- bring broken items
- learn repairs
- volunteer skills
- apprentice informally
Metrics
- landfill diversion
- repairs completed
- skills transferred
- volunteer growth
Landing Page PRD
Hero Headline
“Repairing things together repairs more than objects.”
Primary CTA
Host a Repair Day
Sections
- Why repair culture matters
- How a repair gathering works
- Ecological impact
- Skills and mentorship
- Start locally
- Community stories
3. COMMONS GARDEN NETWORK
Service Requirement Document (SRD)
Vision
Transform fragmented urban land into shared ecological commons that provide food, biodiversity, education, and civic gathering space.
Human Needs
- ecological connection
- stewardship
- nourishment
- participation
- local resilience
Service Components
- food forests
- pollinator corridors
- native habitat
- compost systems
- seed libraries
- stewardship circles
Participation
Residents:
- plant
- maintain
- harvest
- teach
- attend seasonal gatherings
Metrics
- biodiversity indicators
- food production
- participation rates
- pollinator activity
Landing Page PRD
Hero Headline
“Shared land creates shared futures.”
CTA
Start a Commons Garden
Sections
- Why cities need ecological commons
- Food forests and stewardship
- Seasonal rituals
- Education and biodiversity
- Local starter guide
4. CIVIC FIRES
Service Requirement Document (SRD)
Vision
Reintroduce seasonal communal rituals that provide symbolic meaning, emotional containment, and collective reflection.
Human Needs
- grief processing
- ritual participation
- symbolic life
- seasonal awareness
- emotional cohesion
Service Components
- solstice fires
- remembrance gatherings
- storytelling nights
- music/poetry
- silent reflection
Design Principles
- low commercialization
- acoustic-first
- participation over spectacle
- emotional safety
Metrics
- emotional resonance
- repeat attendance
- intergenerational participation
Landing Page PRD
Hero Headline
“A society needs places to gather around meaning.”
CTA
Host a Civic Fire
Sections
- Why ritual matters
- Seasonal rhythms
- Shared grief and celebration
- Gathering format
- Hosting guide
5. THE NIGHT COMMONS
Service Requirement Document (SRD)
Vision
Create calm, non-commercial nighttime environments centered around warmth, presence, conversation, and restoration.
Human Needs
- low-pressure connection
- restoration
- calm sociality
- belonging
Service Components
- tea houses
- reading rooms
- lantern walks
- observatories
- quiet gardens
- ambient music gatherings
Design Principles
- warm lighting
- acoustic softness
- low stimulation
- accessible and affordable
Metrics
- repeat attendance
- perceived restoration
- loneliness reduction
Landing Page PRD
Hero Headline
“Nightlife does not need to revolve around consumption.”
CTA
Create a Night Commons
Sections
- The problem with modern nightlife
- Calm public spaces
- Tea, conversation, reading, music
- Designing for presence
- Community examples
6. THE STORY ARCHIVE
Service Requirement Document (SRD)
Vision
Create a living archive of local memory, oral history, and place-based knowledge.
Human Needs
- continuity
- memory
- identity
- intergenerational connection
Service Components
- recording booths
- oral histories
- memory walks
- projections/installations
- digital archive
Participation
Residents contribute:
- stories
- recipes
- ecological knowledge
- migration histories
- memories
Metrics
- stories collected
- archive engagement
- educational usage
Landing Page PRD
Hero Headline
“A community that remembers itself stays alive.”
CTA
Record a Story
Sections
- Why memory matters
- Oral histories and local knowledge
- Public storytelling
- Intergenerational continuity
- Start an archive locally
7. THE WANDERING WORKSHOP
Service Requirement Document (SRD)
Vision
Create mobile public learning infrastructure that restores apprenticeship, practical knowledge, and embodied learning.
Human Needs
- competence
- mentorship
- embodied learning
- contribution
Service Components
- woodworking
- gardening
- fabrication
- repair
- fermentation
- ecological literacy
Participation
- teach workshops
- attend workshops
- apprentice
- host locally
Metrics
- skills learned
- mentorship formation
- repeat participation
Landing Page PRD
Hero Headline
“A healthy society teaches in public.”
CTA
Host a Workshop
Sections
- Why practical learning matters
- Apprenticeship and public teaching
- Mobile workshop model
- Local activation guide
Shared Technical PRD
Platform Requirements
Architecture Goals
The site should support:
- storytelling
- civic participation
- pattern documentation
- local activation
- eventual chapter/circle systems
- lightweight publishing
- extensibility
Recommended Stack
Assume existing architecture likely includes:
- Next.js App Router
- React
- Tailwind
- MDX/content collections
- Vercel deployment
Preferred Content Model
Each commons initiative should be represented as:
- slug
- title
- subtitle
- problem statement
- ritual layer
- participation model
- CTA
- stories
- implementation guide
- gallery assets
Potential future CMS support:
- Sanity
- Contentlayer
- MDX
- Notion sync
Shared Claude / Codex Prompt Template
Use this prompt as the implementation scaffold.
BUILD PROMPT FOR CLAUDE/CODEX
You are working within an EXISTING codebase and architecture.
Your first priority is to:
- inspect the existing structure
- understand the design system
- identify routing conventions
- identify typography/components/layout primitives
- preserve architectural consistency
DO NOT:
- reinvent the architecture
- create disconnected patterns
- introduce unnecessary dependencies
- replace the design system
- create isolated styles inconsistent with the existing application
INSTEAD:
- extend existing primitives
- reuse components
- follow routing conventions
- maintain visual consistency
- preserve existing information architecture patterns where appropriate
PROJECT CONTEXT
This project is for ICOS / LCOS.
The platform explores:
- commons-oriented civic systems
- regenerative municipalism
- civic rituals
- ecological stewardship
- participatory culture
- social infrastructure
- community resilience
The tone should feel:
- warm
- human
- ecological
- participatory
- grounded
- thoughtful
- calm
Avoid:
- startup aesthetics
- SaaS dashboards
- hyper-corporate visuals
- excessive animation
- gamification
- overly dense interfaces
Visual inspiration:
- field journals
- ecological atlases
- modern civic handbooks
- landscape architecture publications
- tactile editorial layouts
TASK
Build a landing page for: [INSERT INITIATIVE NAME]
Use the following structure:
- Hero Section
- Why It Matters
- How It Works
- Participation Model
- Stories / Imagery
- Start Locally
- Final CTA
REQUIREMENTS
- Mobile responsive
- Accessible
- Semantic HTML
- Reusable components
- Clean typography hierarchy
- MDX/content compatible where possible
- Minimal dependencies
- Strong whitespace rhythm
- Soft transitions only if aligned with current design language
CTA STYLE
Use participatory CTA language such as:
- Start Locally
- Host a Gathering
- Become a Steward
- Bring This To Your Town
- Learn the Pattern
Avoid generic SaaS language.
OUTPUT REQUIREMENTS
- Explain the existing architecture discovered
- Explain implementation decisions
- List reusable components created
- Build production-ready code
- Keep files modular and maintainable
- Follow the current routing/layout conventions exactly
OPTIONAL FUTURE FEATURES
Design with future support for:
- local chapters
- event maps
- story archives
- pattern libraries
- downloadable playbooks
- stewardship circles
- multilingual content
But DO NOT overengineer the first implementation.
Focus on:
- clarity
- emotional resonance
- participation
- extensibility
Suggested Future Folder Structure
/app /patterns /great-feast /great-repair /commons-gardens /night-commons /civic-fires /story-archive
/content /patterns
/components /commons /patterns /stories /cta
Final Strategic Guidance
The goal is not merely event infrastructure.
The goal is:
- rebuilding participatory civic life
- creating modern commons infrastructure
- restoring stewardship and belonging
- reconnecting people to place, ritual, and one another
The implementation should therefore optimize for:
- warmth
- invitation
- participation
- beauty
- adaptability
- local ownership
rather than:
- growth hacking
- engagement maximization
- optimization theater
- corporate branding.