{
  "$schema": "https://pointcast.xyz/for-agents",
  "code": "UES-206",
  "slug": "common-table",
  "title": "Common Table: Hospitality as Civic Infrastructure",
  "status": "active",
  "frame": "Practice invitation, access, facilitation, food or object prompts, conflict care, and follow-through as the working infrastructure of a good collective room.",
  "outcome": "An accessible 45-minute gathering or one-person hospitality rehearsal with an invitation, run-of-show, micro-budget, access notes, and aftercare receipt.",
  "path": "/ues/common-table",
  "jsonPath": "/ues/common-table.json",
  "weeklyCommitment": {
    "selfGuidedStudioMinutes": 75,
    "fieldworkMinutes": {
      "minimum": 60,
      "maximum": 90
    },
    "reflectionMinutes": 20,
    "total": "About 2.5–3 hours per module"
  },
  "access": [
    "Every instruction is readable on the public course page; audio or video references require a transcript or equivalent text path.",
    "Every required prompt, scenario, rubric, and checklist is written on this course page; named sources are optional references, not missing course materials.",
    "Low-bandwidth, print-friendly syllabus with no paid platform or subscription required.",
    "No live attendance, camera, account, wallet, or public posting is required.",
    "Progress stays in this browser unless the learner chooses to download a private completion receipt.",
    "Online-only gathering format and non-food participation path; no learner must host in a private home."
  ],
  "materials": [
    "Tabletop, phone timer, video room, phone bridge, or accessible gathering space",
    "Paper or text file with run-of-show fields: minute, action, purpose, access path, materials, host role, and contingency; budget fields: item, quantity, unit cost, source, total, and $0 alternative",
    "Optional food, flower, image, object, or music prompt",
    "Four optional project microgrants of $100 are included in the course budget"
  ],
  "instructorProfile": "A community producer, hospitality worker, facilitator, or cultural organizer with practical accessibility, conflict-care, budget, and follow-through experience.",
  "soloPath": "Rehearse the gathering alone, with a household member, or as a tabletop walkthrough. Evaluate the invitation, timing, access, budget, and aftercare without requiring guests.",
  "assignments": [
    {
      "title": "Invitation test",
      "dueWeek": 2,
      "brief": "Write an invitation, test it as a first-time participant with no context and as a person using the remote or text-only access path, then revise it. Sending it to a real person is optional."
    },
    {
      "title": "Accessibility walkthrough",
      "dueWeek": 4,
      "brief": "Rehearse the entire arrival-to-exit experience and document barriers, contingency paths, and named host responsibilities."
    },
    {
      "title": "Micro-table rehearsal",
      "dueWeek": 6,
      "brief": "Complete a 45-minute tabletop or solo rehearsal and keep the invitation, run-of-show, micro-budget, access notes, and aftercare receipt private by default. Hosting or publishing is optional."
    }
  ],
  "weeks": [
    {
      "week": 1,
      "title": "Why Should This Room Exist?",
      "question": "What can happen together that should not be another feed, meeting, or performance?",
      "sourceShelf": [
        "On-page purpose test: name what participants can do together, what the room will not ask of them, who benefits, who may be affected, and what trace remains",
        "Examples of salons, teach-ins, kitchen tables, listening rooms, and online circles",
        "Participation, extraction, and host-accountability prompts"
      ],
      "studio": "Distinguish audience, participants, guests, collaborators, hosts, and people affected but absent.",
      "fieldTask": "Compare two on-page scenarios: a first-time guest with no local connections and a guest who cannot travel, appear on camera, or share personal data. Write why each might join, hesitate, or decline. An optional interview may supplement the simulation.",
      "publicReceipt": "A one-paragraph purpose, non-purpose, and promise to participants."
    },
    {
      "week": 2,
      "title": "Invitation, Welcome, Access",
      "question": "What must someone know before saying yes, and what should never surprise them on arrival?",
      "sourceShelf": [
        "Plain-language invitation and access-note examples",
        "RSVP privacy and minimal-data patterns",
        "Online, sensory, mobility, language, food, and care access prompts"
      ],
      "studio": "Write invitations that name purpose, timing, cost, format, access, privacy, recording, and a real contact.",
      "fieldTask": "Check whether the invitation states purpose, date and duration, cost, format, access path, privacy, recording, food or sensory notes, what to bring, and contact; revise every missing answer. Sending it is optional.",
      "publicReceipt": "The tested invitation and a short revision log."
    },
    {
      "week": 3,
      "title": "Shape the Rhythm",
      "question": "How should attention move through forty-five minutes?",
      "sourceShelf": [
        "Run-of-show and facilitation-score examples",
        "Arrival, threshold, small-group, pause, and closing patterns",
        "Timekeeping and online-room production basics"
      ],
      "studio": "Build a minute-by-minute gathering score with a purpose for every transition.",
      "fieldTask": "Time a fifteen-minute tabletop fragment three ways: an expected arrival, a late silent arrival, and a remote or text-only participant. Record where energy, clarity, or access drops. Rehearsing with peers is optional.",
      "publicReceipt": "Run-of-show version one with host roles and contingency branches."
    },
    {
      "week": 4,
      "title": "Host and Facilitate",
      "question": "How does a host share attention without abandoning responsibility?",
      "sourceShelf": [
        "Opening agreements and participatory facilitation prompts",
        "Turn-taking, chat, silence, and small-group methods",
        "Food, object, image, and music prompt examples"
      ],
      "studio": "Role-play arrival, uneven participation, technical failure, dominant voices, silence, and a late guest.",
      "fieldTask": "Walk from invitation through follow-up as someone who cannot use stairs, hear audio, read small type, speak on demand, pay, travel, or identify publicly. Add an equivalent path for every barrier; an optional outside tester may supplement the same check.",
      "publicReceipt": "An access-and-hosting list naming the path, contingency, and host role responsible for each promise."
    },
    {
      "week": 5,
      "title": "Conflict, Care, and Graceful Endings",
      "question": "What can the room hold, and when must the host pause, redirect, or stop?",
      "sourceShelf": [
        "Scope, community agreement, and escalation examples",
        "De-escalation, repair, removal, and referral prompts",
        "On-page aftercare check: close clearly, state follow-up timing, offer correction, store the minimum data, delete practice data, document incidents privately, and refer needs beyond host scope"
      ],
      "studio": "Practice boundary statements, interruptions, repair invitations, endings, and post-event care without pretending hosts are clinicians.",
      "fieldTask": "Write a proportionate response path for three plausible gathering failures.",
      "publicReceipt": "A one-page host care and escalation plan."
    },
    {
      "week": 6,
      "title": "Complete the Table, Keep the Receipt",
      "question": "What should a future participant, funder, or host be able to understand afterward?",
      "sourceShelf": [
        "On-page micro-budget fields: item, purpose, quantity, unit cost, total, payer, reimbursement status, donated value, and $0 alternative",
        "Participant feedback and privacy-minimal evaluation prompts",
        "Reusable host-kit and season-receipt examples"
      ],
      "studio": "Run one full solo or tabletop rehearsal, self-debrief from host and participant viewpoints, and separate private care notes from any optionally shared learning.",
      "fieldTask": "Complete a simulated closeout: reconcile the micro-budget, delete any practice data, and finish the host kit. Real follow-up or reimbursements apply only if the learner optionally hosted guests.",
      "publicReceipt": "A private-by-default invitation, run-of-show, micro-budget, access notes, learning receipt, and reusable source files; hosting or sharing is optional."
    }
  ],
  "archiveWorkNumber": "205",
  "archiveCategory": "HOSPITALITY + COMMONS",
  "connectsFrom": [
    "UES-102",
    "UES-108"
  ],
  "budgetUsd": 3500,
  "addedProductionNeed": "Four $100 optional project grants for access, food, materials, or room costs.",
  "human": "https://pointcast.xyz/ues/common-table",
  "catalog": "https://pointcast.xyz/ues",
  "fundingProgram": "https://pointcast.xyz/university-of-el-segundo",
  "participation": {
    "status": "active",
    "deliveryMode": "self-paced",
    "start": "anytime",
    "durationModules": 6,
    "learnerPriceUsd": 0,
    "requirements": {
      "account": false,
      "application": false,
      "deadlines": false,
      "liveAttendance": false,
      "wallet": false
    }
  },
  "progressPolicy": {
    "storage": "local-browser-only",
    "syncsToServer": false,
    "identityStored": false,
    "learnerArtifactsStored": false,
    "note": "Only completion choices and timestamps are saved in this browser. The learner may reset them or download a private receipt."
  },
  "optionalSupportedCohort": {
    "availableWhenFunded": true,
    "requiredForAccessOrCompletion": false,
    "note": "A scheduled cohort may add human review and facilitation, but it never gates the independent path."
  },
  "completionReceipt": {
    "kind": "self-attested",
    "privateByDefault": true,
    "walletRequired": false,
    "onChain": false,
    "disclaimer": "The receipt is not academic credit, accreditation, verified identity, an on-chain credential, or a financial credential."
  },
  "transactionPolicy": "Course browsing and participation are wallet-free. Tezos support is optional and requires separate explicit Mainnet review."
}