Archive · Tranche 1

EPIC board — the seven proposal workstreams

How the project broke a flawed 40-page proposal into seven bounded workstreams, each with a problem statement, tasks and acceptance criteria — and the board that tracked them, frozen at its last update.

Original title
EPIC Overview — Bottom Pub Co-op, with EPIC-001 to EPIC-007
Original date
EPICs drafted c. 18–20 May 2026; board last updated 4 June 2026
Project phase
Stage 1 — Gauging interest
Purpose at the time
Turn the review of the original operating-model draft into independent, acceptance-tested workstreams (stage discipline, legal structure, licensing, finance, governance, evidence, decision gates) with a steering-level board showing what blocked what.
Status at the time
Board at 4 June 2026: two EPICs in progress (001 messaging, 006 evidence), five not started, none complete. The board was not updated after that date.
Source provenance
Derived from eight private working files: internal/epics/README.md (the board), internal/epics/EPIC-001-stage-discipline-and-public-messaging.md, internal/epics/EPIC-002-legal-structure-and-coop-rules.md, internal/epics/EPIC-003-liquor-licensing-and-regulatory-pathway.md, internal/epics/EPIC-004-financial-model-and-capital-stack.md, internal/epics/EPIC-005-governance-architecture.md, internal/epics/EPIC-006-case-study-and-evidence-base.md and internal/epics/EPIC-007-due-diligence-and-decision-gates.md. All unpublished and unchanged. EPIC-008/009 (website migration and CMS) and the SPEC files are infrastructure, not proposal machinery, and are not included.
Publication treatment
Derived
Derived / prepared by
Claude (Fable 5) with Adrian Wedd, 18 August 2026
Prepared
2026-08-18
Human review
Adrian Wedd — publication review completed 19 August 2026
Published
2026-08-19
What was changed for publication
  • Composite page: the board first, then the seven EPIC files in order, each under its own heading. Text is verbatim; only the relative markdown links between the files (which would be dead here) are unlinked.
  • The board's status column is left as it was on 4 June 2026. Work on several EPICs continued after that date (for example the acquisition-sprint documents and the guardrail screening checklist, both late June 2026) but the board was never updated — the gap between the tracker and the work is itself part of the record.
  • The 'Owner' column was empty in the original for every EPIC. It is left empty.

Document begins

EPIC Overview — Bottom Pub Co-op

Internal | Last updated: 2026-06-04

This document is the steering view of the project’s EPIC structure. Each EPIC is an independent workstream with its own acceptance criteria. Update status here when work moves.


Status key

SymbolMeaning
⬜ Not startedNo work begun
🔵 In progressActively being worked
🟡 BlockedWaiting on a dependency or external input
🟢 CompleteAcceptance criteria met
⛔ SupersededReplaced or no longer relevant

EPIC board

#TitleStatusOwnerBlocksBlocked byNotes
001Stage Discipline & Public Messaging🔵 In progressOngoing gate on all public releases
002Legal Structure & Co-op Rules⬜ Not started004, 005Options paper for solicitor review; decision gates on capital design
003Liquor Licensing & Regulatory Pathway⬜ Not startedTasmanian licence-holder requirements; AR-27 reform status
004Financial Model & Capital Stack⬜ Not started002, 007No forecast without assumptions; investor-return language quarantined
005Governance Architecture⬜ Not started002Role map + decision-rights matrix; AR-23 sociocracy risk
006Case Study & Evidence Base🔵 In progressAR-12/AR-13 corrections applied; Hotel Theodore failure included
007Due Diligence & Decision Gates⬜ Not started002, 003, 004, 005Stage-gate roadmap; go/no-go criteria
008Website Migration to Astro⬜ Not startedScalability; ~15 HTML files with duplicated nav/footer
009Emdash CMS Adoption⬜ Not startedAstro + CF CMS layer; Phase 0 spike gates go/no-go; may supersede EPIC-008

Critical path (Stage 1 → Stage 2 boundary)

Property status confirmed (AR-05)
    └─► EPIC-007 (Decision Gates) gates Stage 2 entry
            ├─ EPIC-002 (Legal) → unlocks capital design
            ├─ EPIC-003 (Licensing) → confirms venue viability
            ├─ EPIC-004 (Finance) → depends on legal structure
            └─ EPIC-005 (Governance) → depends on legal structure

EPICs 001 and 006 run as continuous guardrails across all stages. EPICs 008 and 009 are infrastructure — not on the critical path, but reduce maintenance risk as the site grows. EPIC-009’s Phase 0 spike determines whether it supersedes EPIC-008.


Open cross-EPIC risks

RiskRelevant EPICsRegister entry
Property may not come to marketAllAR-05
Legal structure choice (distributing vs non-distributing) ungated002, 004, 005AR-14
Sociocratic governance incompatible with CNL005AR-23
Earlier financial promises still held by community members001, 004AR-22
Charitable status assumption ahead of legal advice004AR-28

How to use this board

  • Assign an owner to each EPIC when a steering committee member takes it on.
  • Update status at each fortnightly check-in.
  • Do not mark an EPIC complete unless acceptance criteria in its own file are met.
  • Do not start EPIC-004 or EPIC-005 before EPIC-002 produces its options paper.

File EPIC-001 follows.

EPIC-001 — Stage Discipline and Public Messaging

Problem

The short proposal correctly frames the project as an early idea, but the long operating model jumps ahead into investor returns, exact salaries, and long-term outcomes.

Goal

Keep all public-facing material aligned to Stage 1: gauging interest.

Tasks

  • Audit all public copy for stage leakage.
  • Add “not an investment offer” language.
  • Create public FAQ.
  • Create message hierarchy.
  • Create review checklist for future public releases.

Acceptance criteria

  • No public draft claims purchase feasibility, investor returns, fixed capital requirements, or guaranteed governance structure.
  • All future-facing claims use careful conditional language.
  • Public copy remains warm and inviting, not legalistic sludge.

File EPIC-002 follows.

Problem

The proposal blends distributing/non-distributing co-op features, community benefit, member rebates, investor returns, and democratic control without a settled legal structure.

Goal

Prepare an options paper for professional legal review.

Tasks

  • Compare distributing vs non-distributing co-op implications.
  • Define possible active-membership models.
  • Identify constraints on shareholding and voting.
  • Draft solicitor questions.
  • Map consequences for surplus, rebates, grants, and investor capital.

Acceptance criteria

  • Options are clearly separated from recommendations.
  • Each option lists benefits, risks, unanswered questions, and professional-review needs.
  • No legal conclusion is presented as final without advice.

File EPIC-003 follows.

EPIC-003 — Liquor Licensing and Regulatory Pathway

Problem

Tasmanian liquor licensing appears to require an individual licence-holder, not a company/trust. The co-op model must account for this.

Goal

Build a licensing/regulatory pathway memo.

Tasks

  • Verify Tasmanian licence-holder requirements.
  • Identify licence type likely required.
  • Determine transfer vs new application questions.
  • Map RSA, effective control, community-interest, food, planning, and public-notice requirements.
  • Prepare questions for licensing adviser.

Acceptance criteria

  • Licensing assumptions are sourced.
  • Memo distinguishes confirmed rules from questions.
  • Proposal wording avoids implying the co-op itself can simply hold/run the licence.

File EPIC-004 follows.

EPIC-004 — Financial Model and Capital Stack

Problem

The current long document contains fixed financial claims without enough assumptions or due diligence.

Goal

Replace false precision with an assumptions-first financial framework.

Tasks

  • Build acquisition/capex/working-capital assumption categories.
  • Build conservative/base/upside scenario template.
  • Identify revenue drivers: bar, food, events, accommodation, memberships.
  • Identify cost drivers: wages, COGS, utilities, insurance, repairs, debt service.
  • Create capital-stack options list: member shares, grants, loans, debentures, donations, social finance.
  • Remove fixed returns from public material.

Acceptance criteria

  • No forecast is presented without assumptions.
  • All numbers are labelled as placeholder, estimate, source-backed, or verified.
  • Investor-return language is quarantined for professional advice.

File EPIC-005 follows.

EPIC-005 — Governance Architecture

Problem

The proposal has a strong ownership/management distinction, but the decision-rights model needs tightening.

Goal

Create a governance architecture that locals can understand and professionals can implement.

Tasks

  • Create role map: members, board, publican, staff, worker members, investors, committees/circles.
  • Create decision-rights matrix.
  • Resolve investor board-seat tension.
  • Define what members vote on and do not vote on.
  • Define escalation pathways for ideas and concerns.

Acceptance criteria

  • Governance model prevents operational micromanagement.
  • Democratic control remains clear.
  • Investor influence is limited and transparent.
  • Public-facing version is simple enough for a community meeting.

File EPIC-006 follows.

EPIC-006 — Case Study and Evidence Base

Problem

The long document uses examples and numbers that may be persuasive but need verification.

Goal

Create a verified evidence base.

Tasks

  • Verify each named case study.
  • Separate direct analogues from loose inspiration.
  • Prefer official sources.
  • Add caveats for UK/non-Australian examples.
  • Remove unverified claims.

Acceptance criteria

  • Every public case-study claim has a source.
  • Unverified examples are removed or marked internal-only.
  • Comparative evidence is not overstated.

File EPIC-007 follows.

EPIC-007 — Due Diligence and Decision Gates

Problem

The proposal needs a disciplined pathway from idea to feasibility to possible acquisition.

Goal

Define staged decision gates.

Tasks

  • Create stage-gate roadmap.
  • Define evidence required at each stage.
  • Define go/no-go criteria.
  • Define roles for steering group, advisers, and community meetings.
  • Create a public progress dashboard outline.

Acceptance criteria

  • No stage proceeds without evidence requirements.
  • Go/no-go decisions are explicit.
  • Community trust is protected through transparent reporting.
End of document ← Back to the archive