Two‑Sentence Gist
LOSCs are small, merit‑driven, rapidly deployable communities that run on 7 Components and a simple 3‑rank structure—Assistant, Field Operator, Unit Commander—for clear action and accountable leadership.
They’re designed for scarcity or crisis, scale from ≈24 people up, and elevate decision‑makers by affidavit from the community rather than top‑down appointment.
Clean Outline
- Purpose & scale: why LOSC, when to form, size (≈24+), how to branch when hundreds.
- 3 Ranks: Assistant/Apprentice → Field Operator → Unit Commander (affidavit‑based promotion; campaign from below).
- Promotion logic: proofs of competence, “rule of 3” practica, campaign status, referenda by affidavit.
- 7 Components: Mentallics, Agriculture, Care, Militia, Administration, Engineering, Cybernetics.
- Governance notes: meritocracy that escalates to a republic; multiple titles possible; recommend distinct UCs per component.
- Spin‑up checklist: minimum crew, first‑week tasks, comms rhythm, handoffs, accountability loop.
Forming a LOSC
Purpose & scale
A LOSC is a small, fast, and pragmatic community structure for scarcity or crisis (fire, flood, hostile force, supply collapse). Operate with ≈24 people or more; below ≈24, merge with neighbors. Once you reach several hundred, fork into regional LOSCs with the same pattern.
The 3 Ranks
1) Assistant or Apprentice
- Baseline doer under supervision; proves reliability by following standards and delivering consistent outcomes.
- “Apprentice” = an Assistant who has declared intent to promote; same duties, higher bar.
- Must operate with at least one Field Operator; not held solely responsible for outcomes.
Promotion to Field Operator
- Customary path: show competence under three different Field Operators (“rule of 3”).
- Promotion typically by Unit Commander affidavit after consistent practicum at FO level.
2) Field Operator (FO)
- Can work alone, lead small teams, and act as Acting UC if only FOs are present (senior FO leads).
- Trains Assistants/Apprentices and ensures standards in the field.
3) Unit Commander (UC)
- Decision bottleneck for the component; accountable to the community.
- Promotion requires community affidavits; UCs yield to candidates with more affidavits (even without a simple majority).
- Only FOs can campaign for UC; UCs cannot appoint UCs. Campaign from below; be chosen by those you serve.
Note: A person can hold multiple titles across components, but in practice each component should have its own UC.
The 7 Components
For each component, responsibilities are split by rank:
- Assistant / Apprentice — execute tasks to standard under FO supervision.
- Field Operator — run operations independently; mentor; maintain standards.
- Unit Commander — set priorities, allocate people/resources, report results to the community.
1) Mentallics community intelligence
- Assistant: complete targets; maintain measurable hit‑rate on known targets.
- FO: design tasking, run projects, synthesize findings.
- UC: align questions to community needs (e.g., locate aid, assess external risks), publish clear briefs.
2) Agriculture food & forage
- Assistant: soil prep, planting to spec; harvest.
- FO: crop planning, water/soil management, tool & seed stores; coordinate foraging.
- UC: caloric planning for population, redundancy (seed banks, soil inputs), trade posture.
3) Care children, elders, injured
- Assistant: daily care routines, logs, sanitation.
- FO: triage protocols, schedules, special‑needs plans, safe‑room setups.
- UC: capacity planning, duty rosters, mutual‑aid agreements with adjacent LOSCs.
4) Militia protection & order
- Assistant: post duty under FO; observe/report; basic de‑escalation.
- FO: perimeter plans, patrol routes, contact protocols; detain/transfer procedures aligned to standards.
- UC: rules of engagement ratified by community, after‑action reviews, liaison to Administration.
5) Administration records & sovereignty
- Assistant: maintain logs, inventories, affidavits, rosters.
- FO: charter upkeep, dispute intake, meeting agendas/minutes.
- UC: cadence of referenda, affidavit validation, inter‑component coordination.
6) Engineering power & mechanics
- Assistant: generator checks, fuel/water handling, tool maintenance.
- FO: build/repair (power, pumps, wheels), preventive maintenance schedules.
- UC: resilience planning (spares & skills map), project prioritization.
7) Cybernetics comms & p2p
- Assistant: radio checks, device prep, basic key handling.
- FO: mesh setup, long‑range links, encrypted channels, data backups.
- UC: comms doctrine (who talks to whom & when), inter‑LOSC relays, information integrity.
Spin‑Up Playbook — First 7 Days
Day 0–1
- Confirm headcount (≥24) and map existing skills to components.
- Nominate interim FOs (based on past competence); open Assistant/Apprentice intake.
- Set daily check‑in cadence (15–30 min / component).
Day 2–3
- Each component publishes a 1‑page Minimum Operating Standard (MOS).
- Begin affidavit collection for any UC candidates (Administration runs process).
Day 4–5
- FOs run operations to MOS; Assistants rotate through at least two FOs.
- Draft mutual‑aid ask/offer list for neighboring LOSCs (Agriculture, Engineering, Cybernetics, Care).
Day 6–7
- Community affirms UCs via affidavits; publish roster & contact tree.
- Hold first cross‑component review; adjust MOS; set 14‑day goals.
Minimum Charters
- Merit → Trust → Responsibility.
- Affidavits legitimize authority.
- One UC per component (practicality first).
- Document everything that affects food, safety, power, or comms.
- Branch, don’t bloat: when big, split into sibling LOSCs with identical pattern.
Must‑Keep Checklist
- Thresholds & branching: ≈24+ to function; fork at several hundred.
- Rank logic & affidavit promotions (campaign from below; UCs yield to higher‑affidavit candidate).
- “Assistant vs Apprentice” distinction (same job; declared intent to promote).
- All 7 named Components, with Mentallics as disciplined community intelligence.
- Multiple titles possible, but recommend separate UCs per component.
License & Reuse
Free to copy, remix, and deploy for community resilience. Please keep attribution to the LOSC pattern and share improvements forward.