3.4 Agenda Template (90 min)

1. Opening (10 min) — recap last artifact; one line each on how it landed.
2. Reading (20 min) — Reader presents text/page; questions clarifying only.
3. Relating (20 min) — Practitioners connect to lived contexts (workflows, families, media).
4. Rehearsal (30 min) — roleplay, draft, or prototype artifact.
5. Recording (10 min) — Recorder finalises; schedule next micro-release.

3.5 Role Cards

• Anchor: keep the pace, enforce 90-minute max.
• Reader: bring one prepared passage with why it matters.
• Practitioner: translate passage into lived workflow.
• Recorder: distil to a 1-page artifact with version/date.
• Rotator: each week, roles rotate clockwise.

3.7 Circle OS Tools

• /agenda — auto-template with timeslots.
• /artifact log — versioned list of circle outputs.
• /rotation — tracks who holds which role next week.

3.8 Success Metrics

• At least 1 artifact/week shipped.
• At least 80% rotation (everyone plays every role within 8 weeks).
• Circle continuity: 75% attendance across 12 weeks.

4.1 Editorial Protocol

1. Brief: 1-page prompt with thesis, audience, evidence.
2. Draft: single pass, timestamped, stored in /drafts.
3. Proof Stack: attach sources (metadata only) + screenshots.
4. Review: 2 peers sign off on clarity & accuracy.
5. Release: publish with version ID (v1.0, v1.1 etc).

4.2 Content Types

• Briefs: 600–800 words; sharpen thinking.
• Guides: 1,500–3,000 words; execution focus.
• Artifacts: checklists, templates, posters.
• Logs: release notes for transparency.

4.4 Proof-First Culture

• No hot takes: every claim has a source in proof stack.
• No ghost edits: all changes logged with version IDs.
• Peer sign-offs: 2 people verify clarity before release.

4.5 Media Metrics

• Latency: time from draft → release (goal < 7 days).
• Integrity: % of releases with full proof stacks (goal 100%).
• Reach: views/downloads vs. circle size (goal 3× multiplier).

5.1 Daily Discipline Loop

1. Inputs: What did I study, practise, or produce today? (pages, reps, drafts).
2. Integrity: What did I check? (sources, peer review, testing).
3. Impact: Who benefited today? (user, team, community) — with evidence.

Close with one line: “What did common sense push me toward? What would good sense have done?”

5.2 Log Formats

• /daylog — single page; input/integrity/impact + reflection.
• /weeklog — 7-day roll-up; highlight 2–3 patterns.
• /craft log — track one skill (e.g., writing, coding) with metrics.

5.4 Example: Writer’s Log

• Inputs: 3 pages read (Gramsci), 600 words drafted.
• Integrity: 2 claims cross-checked with sources.
• Impact: Draft shared in circle, 1 peer used in meeting.
• Reflection: “Common sense: skip citations. Good sense: proof-first.”

5.5 Example: Developer’s Log

• Inputs: 90 minutes coding; read 1 API doc.
• Integrity: Ran 12 tests; 11/12 passed.
• Impact: Feature live; 10 users touched it today.
• Reflection: “Common sense: rush release. Good sense: pause for tests.”

5.7 Discipline Metrics

• ≥ 70% of days with complete logs.
• ≥ 1 craft KPI trending upward every 4 weeks.
• ≥ 1 reflection per week adopted into circle artifact.

5.8 Failure Portfolio

Track safe failures (attempts where risk = low, learning = high). Record:

• Context: what was attempted
• Cost: time/resources lost
• Learning: what changed next time

Failure logs stop shame spirals; they turn loss into scheduled tuition.

6.1 Alliance Map (Who & Why)

Plot partners by mission fit and execution reliability. Start small; grow by proof.

6.2 Minimum Viable Federation (MVF)

• Common Calendar: public read-only ICS of releases and circle slots.
• Artifact Registry: a page listing title, version, date, owner, license.
• Protocol Deck: 5–7 SOPs (naming, review, accessibility, proof stacks).
• Ethics Card: lawful, respectful discourse; no brigading; platform ToS first.

6.4 Interop: How Circles Plug Together

1. Shared Prompts: keep the same role prompts (read → relate → rehearse → record).
2. File Naming: YYYY-MM-DD_title_v1.0_circle-id.
3. Release Notes: each artifact ships with a 5-line change log.
4. Accessibility: alt text, headings, plain-English summary.

6.5 Joint Release Pipeline

1. Circle A drafts → Circle B peer-reviews.
2. Proof stack compiled (citations in metadata only).
3. Legal/ToS check → License set.
4. Publish on both sites with canonical link.
5. Post a federation log entry (who/what/when/metrics).

6.7 Conflict & Credit

• Disputes: 24-hour cool-off → 15-minute mediation with Anchor from a neutral circle.
• Credit: list contributors alphabetically unless a lead is formally assigned.
• Retract/Amend: version bump with reason in release notes; never stealth-edit.

6.8 Security & Privacy

• Use least-privilege access on shared drives; restrict raw data.
• Strip PII from artifacts; aggregate sensitive stats.
• Checksums/hashes on PDFs for tamper-evidence.

6.10 Joint Campaign Pattern

1. Theme: literacy, discipline, or community health.
2. Artifacts: poster + checklist + brief.
3. Activation: 2 workshops across partner sites.
4. Evidence: simple pre/post survey; publish anonymised results.

6.11 Exit & Succession

• Any circle can pause with a short note in the federation log.
• Artifacts remain under their license; maintain canonical links.
• Encourage split & seed: alumni start new circles with the core protocol deck.

7.1 Factory Study Circle (Historical)

In 1920s Turin, workers ran factory councils with reading groups. Instead of slogans, they produced technical manuals and worker newspapers explaining processes in plain language.

• Inputs: literacy training + technical notes.
• Integrity: peer-checked against machinery manuals.
• Impact: improved safety + worker leverage in negotiations.

7.2 Modern Community Library Circle

A circle of librarians + parents ran a weekly reading-tech lab in a small town. Each week, they created one-page “how-to” sheets (search safely, evaluate sources, use citation tools).

• Inputs: 90-minute sessions; 10–12 participants.
• Integrity: fact-checked sheets before distribution.
• Impact: 200+ downloads in 3 months; local school adoption.

7.3 Software Team Discipline Logs

A dev team embedded /daylog into Slack. Each log captured inputs (code commits), integrity (tests run), and impact (tickets closed). Peer review was attached as proof stacks.

• Inputs: 15–20 commits/day across 6 devs.
• Integrity: 95% test coverage maintained.
• Impact: 30% drop in bug reports over 2 months.

7.4 Student Federation Across Campuses

Three student groups agreed on a federation MoU. They shared reading lists, artifact templates, and editorial calendars. Each campus produced its own briefs, then released a joint “Student Commons Handbook.”

• Artifacts: 12 briefs + 1 joint handbook (v1.0).
• Distribution: hosted on all 3 university websites.
• Impact: Handbook cited in student policy doc; 500 downloads.

7.6 Health Circle (Applied Today)

Community health workers formed a study circle around nutrition and exercise. Each week they shipped micro-artifacts (meal prep checklists, 15-min stretch routines).

• Inputs: 4 readings + 1 workshop/week.
• Integrity: validated with NHS guidelines.
• Impact: 60 seniors attended; reported improved energy.

7.7 Federation Across NGOs

Two NGOs shared a federation log. They co-published literacy posters in multiple languages. Each artifact carried version IDs and Creative Commons licenses.

• Artifacts: 6 posters, translated into 5 languages.
• Distribution: printed + digital; 1,500 copies circulated.
• Impact: adoption in 8 community centres; measurable literacy gains.

Q1. What does “hegemony” mean in daily life?

It’s the common sense baked into routines — calendars, phrases, defaults. You shift it by upgrading practices, not just arguing.

Q2. What’s a “study circle” in this system?

A weekly 90-minute group (5–9 people) using read → relate → rehearse → record. Output = one micro-artifact (e.g., checklist).

Q3. How is this lawful?

All practices are educational, cultural, and lawful. No harassment, no manipulation, no ToS violations. Focus = literacy, craft, and respectful discourse.

Q4. How do we measure success?

Three metrics: Inputs (what you practised), Integrity (how you checked), Impact (who benefited). Track in logs and dashboards.

Q5. How does “federation” differ from centralisation?

Federation = many circles sharing protocols + artifacts. No central authority; circles stay autonomous but interoperable.

Q6. Do artifacts need citations?

Yes. Proof stacks required. Citations live in metadata (JSON-LD, release notes) so design stays clean while sources are traceable.

Q7. How do I start if I’m alone?

Begin with a personal log (inputs/integrity/impact). Publish one micro-artifact in 7 days. Invite 1–2 peers to review. That’s your seed circle.

Q8. What’s the minimum viable output?

One page: clear heading, 3–5 steps, version/date, and proof sources. Share as PDF or web post with canonical link.

Q9. How do we handle disagreement?

24-hour pause → 15-minute mediation by a neutral Anchor. If unresolved, publish both positions in release notes; no stealth edits.

Q10. Isn’t this just activism?

No. This is craft-first. Circles build usable artifacts — guides, protocols, checklists — that improve daily literacy and discipline.

9.6 Editorial Brief Template

Title:
Thesis:
Audience:
Evidence:
Format: (brief, guide, poster, log)
Version: v0.1
Due Date:
Reviewers:
    

9.7 Release Notes Template

Artifact: [Title v1.1]
Date: YYYY-MM-DD
Changes:
- [List changes]
Reason for update:
Reviewed by:
    

10.2 Phase 1 — Audit (Weeks 1–2)

• Run the 4T Audit (Time, Talk, Tools, Tokens).
• Collect 48h samples; tag help/hinder.
• Launch 3 habit experiments (notifications, language, naming).
• Output: Good Sense Charter (one page).

10.3 Phase 2 — Circle (Weeks 3–5)

• Form circle (5–9 people, weekly 90 mins).
• Roles: Reader, Practitioner, Recorder, Anchor.
• Ship 1 artifact/week (brief, checklist, poster).
• Rotate roles weekly for 80% coverage.

10.4 Phase 3 — Media OS (Weeks 6–8)

• Adopt editorial protocol (brief → draft → proof stack → release).
• Build 90-day editorial calendar.
• Require 2 peer sign-offs per release.
• Output: Editorial protocol doc + proof stack system.

10.5 Phase 4 — Discipline (Weeks 9–10)

• Run daily /daylog + weekly /weeklog.
• Launch craft KPI dashboard (inputs, integrity, impact).
• Start failure portfolio (≥ 3 safe failures).
• Output: KPI dashboard + failure portfolio entries.

10.7 Discipline Routines (Throughout)

• Morning reset (pick focus).
• Midday check (adjust course).
• Evening log (inputs → integrity → impact).
• Weekly reflection shared in circle.

10.8 Guardrails

• Lawful: education, literacy, cultural improvement only.
• Respectful: no harassment; credit all contributors.
• Transparent: no stealth edits; publish release notes.
• Accessible: alt text, clear headings, plain-English summaries.

11.1 Family & Inner Circle

Begin with logs at home. Share one artifact per week with family or closest allies — a checklist, a prompt deck, a reflection sheet. Hegemony shifts first at the dinner table and in daily talk.

11.2 Ritual & Literacy

Create rituals around reading and rehearsal. 20 minutes daily reading + 90 minutes weekly circle = minimum viable literacy engine. Keep artifacts portable, plain, and proof-first.

11.3 Discipline & Logs

Run daily /daylog and weekly /weeklog. Track inputs, integrity, and impact. Publish small wins, not slogans. Let logs accumulate into habit capital that resists drift.

11.4 Media OS

Adopt editorial protocols: briefs → drafts → proof stacks → releases. All artifacts carry version IDs, release notes, and licenses. Transparency beats hot takes.

11.5 Federation & Alliances

Link circles via shared calendars, artifact registries, and MoUs. Keep federation logs transparent. Avoid centralisation; strengthen autonomy through interoperability.

11.6 Community Health Execution

Measure success by cultural health: literacy rates, participation in study circles, shared rituals of care. Federation is not abstract politics — it is community resilience in practice.