CLOSE THE GAP — PROJECT CHARTER

Project: CLOSE THE GAP
Goal: Doomsday survival tech (goal_732163d70399)
Program of record: Fallout Protocol
Commissioned: Chris, Mon Nov 2, 2026, ~07:39 EST — “Let’s make this a project.”
Charter filed: 2026-11-02
Founding state: W0 STAGED — NOT WALKED · household tier UNVERIFIED

Name proposal, not a rename: FALLOUT PROTOCOL: CLOSE THE GAP is the better-founded house form because the governing pack, daily watch, and program journal already live under the Fallout Protocol name. The working name in this charter remains CLOSE THE GAP unless the owner rules otherwise.

1. Purpose

Japan’s Nov 2, 2026 urgent preparedness request names the ordinary physical basics a household is expected to hold for itself: at least three days — ideally one week — of water and food, portable-toilet supplies, and a rolling stock, alongside hazard knowledge, a go-bag, and drills. This house already has an unusually strong information layer: local-first apps, an offline knowledge pattern, local AI, weather tooling, RF tooling, and records that remain usable without a platform’s permission. What the house has not proven is the corresponding physical layer — counted water, backup watts, and working radio reach. CLOSE THE GAP closes those gaps in the Fallout Protocol’s own order: survey first, water next, then power, radio reach, the unfinished $0 software, and the remaining household kit. It is not a shopping project and it does not manufacture a readiness claim: every physical line remains UNKNOWN until the owner’s Act Zero report counts it, and every later claim carries that OWNER-REPORTED provenance.

2. Governing evidence

2.1 The Fallout Protocol Checklist — the working surface

~/workspace/fallout-protocol/CHECKLIST-2026-10-28.md

• The checklist’s inventory fence is absolute:

“Every household stock is UNKNOWN until Act Zero counts it. A box is checked only against a counted, dated survey line — never against memory, never against ‘we probably have some.’ An uncounted line reads GAP — UNKNOWN, which means neither zero nor stocked.”

• The household planning rates are 3 gal of water/day and ~5,400 kcal/day for Chris, Mircy, and Rin.
• The tier shape is cumulative:
• T1 — 3 days: 9 gal · ~16,200 kcal.
• T2 — 7 days, the center of gravity: 21 gal · ~37,800 kcal.
• T3 — 30 days: 90 gal, or 42 gal plus a rehearsed resupply/boiling method · ~162,000 kcal.
• T4 — 90 days: systems and specifics depth, not a literal 270 gal / ~486,000 kcal stockpile strategy.
• Act Zero is lines AZ-1 through AZ-14: walk, count, locate, date, write consumption rates where knowable, compile one GAP list, and only then print the household’s verified tier.

2.2 The Fallout Protocol — postures, quantities, and chains

~/workspace/fallout-protocol/FALLOUT-PROTOCOL-2026-10-28.md

• The plan’s headline is:

“The 7-day hurricane tier (Tier 2) is this plan’s center of gravity. Build to 7 days first, completely, in the spine’s binding order.”

• Its empirical order is water/sanitation first; prescription and power-dependent care continuity next; heat/cooling after power loss; generator carbon monoxide; cash/payment failure; fuel; information; then food as a short-event constraint.
• Its honest state line governs this project:

“Against this plan, the household’s known state is UNKNOWN almost everywhere … These print as GAPS — never as assumed-zero and never as assumed-stocked.”

• The Protocol does not make Japan’s 3 L/person/day drinking-water figure the house sizing rule. The house rule remains the Protocol’s 1 gal/person/day — drinking plus basic hygiene/cooking, with Rin counted at the full gallon and Florida heat treated as making 3 gal/day a floor, not a ceiling.

2.3 The App Layer — what exists, what is absent, and the inventory-app spec

~/workspace/fallout-protocol/APP-LAYER-2026-10-28.md

• Part A records Kiwix and a vendored ZIM shelf as IN HAND, with the server half re-proven in that pass and the two-device household-reading half still pending owner devices.
• Part A’s named absences include:
• off-grid radio comms: no function today on that record;
• weather reception: absent on the fleet record;
• CoMaps Florida map data: adopted-not-stood-up, data not in hand;
• any household supply / inventory / preparedness-checklist app: not inventoried.
• Part B defines the missing product as:

“a capture-first inventory + tier-checklist + burn-rate timer whose value is created at the shelf, in advance, in ~20-second entries”

• The same spec names the danger this project’s order must avoid:

“An inventory app whose inventory was never entered is a checklist with zeroes — worse than no app, because it looks like knowledge.”

• The app’s privacy line is binding on W4/W5:

“The app tracks supplies, never people … Rin’s data rules are untouched and uninvolved: nothing about Rin is recorded by this app, no child surface exists…”

2.4 The Oct 21 resilience study — the gap diagnosis and hunt ground

~/workspace/security-desk/resilience-field-guide.md · ~/workspace/security-desk/resilience-tech-survey.md

The tech survey’s fleet conclusion is the project’s diagnosis:

“The resilience gap in this house is not software. It is water, watts, and radio reach…”

The field guide sets the local case: Winter Haven’s realistic disruption is a hurricane-season event involving multi-day grid outage, flooded roads, water disruption, and no internet. It also preserves the owner-input fence: medications, documents, pets, powered medical equipment, evacuation host, and flood posture are asked, never assumed.

The study’s OWNER-HUNT prices are stale market ground as of Oct 21, 2026, not current prices and not purchase authority. Any price the project eventually uses must be read live at proposal time. See Appendix A.

3. Founding baseline — what may and may not be claimed

No founding claim upgrades a dated source. A source dated Oct 21 or Oct 28 proves what it recorded then; W0 and each workstream fixture establish the Nov 2-and-after state.

4. Project order and gates

W0  ACT ZERO SURVEY
    └─ gate: no physical-stock claim, tier claim, or gap-closing purchase
       proposal is valid before the owner’s dated report is graded
        ├─ W1  WATER
        ├─ W2  WATTS
        ├─ W3  RADIO REACH  ── consumes OQ-104; does not re-decide it
        ├─ W4  SOFTWARE FINISHES ── kit app waits for W0 data
        └─ W5  KIT & TOOLS ── dispositions every remaining W0 GAP

The workstreams are worked in this order. A later workstream may prepare paper, specs, or a fixture while an earlier one waits on the owner, but it may not declare a physical gap closed out of order or from an uncounted assumption.

Project-level definition of done

CLOSE THE GAP is done only when all of the following are true:

1. Act Zero is filed with every AZ line either counted or explicitly left GAP — UNKNOWN, and the household’s verified tier is printed from the counted lines.
2. W1 reaches at least the Tier 2 water posture, or every shortfall remains printed as a named GAP with its reason.
3. W2 has a tested backup-power and light posture for the loads the owner chooses to protect, under the Protocol’s CO and electrical-safety rules.
4. W3 has a working receive/information layer and a printed contact plan; its mesh state exactly mirrors the owner’s OQ-104 ruling and any resulting fixture.
5. W4’s four software finishes each pass their stated fixture; none is called done from an install alone.
6. W5 dispositions every remaining Checklist section line as MET — counted, GAP — owner chose not to close, or GAP — UNKNOWN, with Rin’s §12 handled as a standalone paper/household section.
7. A review date is set for rotation, expiry, medication windows, destinations, and the GAP list. The Protocol’s cadence itself remains a proposal until the owner adopts a project review cadence.

5. Standing fences — the whole project

1. $0 standard. Software and preparation proceed at $0. Any hardware purchase returns as a separate priced proposal, read live at purchase time, with the owner’s ruling per item.
2. Stale-price fence. Prices in the Oct 21, 2026 study and the Oct 2026 Protocol appendix are ground for judging a live price, never quotes. Each is labeled with its as-of date wherever cited.
3. No pre-W0 inventory claim. No agent states that the house has, lacks, or has a number of any physical stock before the owner’s W0 report grades it. “Not on the record” is not converted into “not in the house.”
4. OWNER-REPORTED provenance travels. Every count, location, date, rate, and days-of-cover figure derived from the walk is labeled OWNER-REPORTED with the survey date. Muse’s arithmetic does not upgrade the underlying count to VERIFIED.
5. Unknown means unknown. A line that cannot be found, opened, read, or counted stays UNKNOWN. An estimate is printed ESTIMATED and is never used to check a box.
6. Rin’s data never moves. The project records only the household supply facts her parents choose to state for Checklist §12. No measurement of Rin, no diagnosis material, no photographs of Rin or her personal boards/content, and no Rin data in the kit-inventory app.
7. Private household facts stay private. Medication names/doses, cash totals, document contents, and account details are not placed in shared project records. The checklist method records counts, days on hand, refill windows, locations, and Y/N states only where the household chooses.
8. Safety rules are not proposals. Generator use, if a generator is ever present or acquired, is outdoors only, at least 20 ft from windows/doors/vents, exhaust away, never in a home/garage/basement, with a working CO alarm. No backfeeding. Candles are not the light plan.
9. No external action. Nothing about this project posts, messages, files a license, contacts a seller, or buys anything. The GMRS license, if pursued, is filed by the owner himself.
10. Corrections are dated addenda. A later count supersedes an earlier one by a dated replacement line; the earlier report is not silently rewritten.

6. Workstreams

W0 — ACT ZERO SURVEY

Objective. Convert the household’s physical state from UNKNOWN almost everywhere into a dated, owner-reported inventory and GAP list. The staged field instrument is ACT-ZERO-SURVEY-KIT-2026-11-02.md in this folder.

What done looks like

• AZ-1 through AZ-14 are each answered by a count, a location, a date, a Y/N state, or an explicit GAP — UNKNOWN.
• Water days of cover are calculated as counted gallons ÷ 3.
• Food days of cover are calculated as counted shelf-stable kcal ÷ ~5,400.
• Each counted specific with a known use rate gets units on hand ÷ units per day.
• The household’s verified tier is printed only from counted essential lines; if any essential line remains unknown, the tier prints UNVERIFIED and names the blocking lines.
• The GAP list — not the hoped-for tier — becomes the input to W1–W5.

What it needs from the owner

• Hands/time: one room-by-room walk, estimated in the survey kit at 90–130 owner-minutes, ESTIMATED.
• Reports: counts dictated in chat or photographs of shelves, containers, and labels, subject to the kit’s privacy limits.
• Facts only the household has: medication days/refill windows without drug names on the shared record; cash counted Y/N or a total only if the owner chooses; document locations; cooling destinations; vehicle road-readiness; home construction and most-interior room; Rin supply-class applicability by her parents’ word.

Fences

• No estimating on the walk.
• No photographs of prescription labels, identity documents, cash, Rin, or Rin’s personal communication content.
• A thing not found during the walk is not found on the walk, not proven absent from the house, unless the owner explicitly verifies absence.

W1 — WATER

Objective. Close the scenario runs’ binding constraint first: drinking-water storage, clean receiving capacity, a non-drinking hygiene tier, and a rehearsed treatment/resupply path.

What done looks like — Tier 2 acceptance first

• At least 21 gal of drinking water is stored in food-grade containers.
• Container locations are reported and known to both adults; the storage place is chosen for the T2 load — approximately 175 lb of water — not merely for convenience.
• Fill/rotation dates are recorded for every container.
• The boil-vs-chemical fork is printed and posted with the household plan:
• Boil Water Advisory = microbial; rolling boil 1 minute works.
• Do Not Drink / Do Not Use = chemical; boiling does not work and can concentrate contaminants; stored/distributed water only.
• A second, non-drinking water tier is identified for hygiene/flushing where the home allows it.
• Empty food-grade receiving containers are held for distributed water.

Stretch acceptance — Tier 3

• Either 90 gal stored, or 42 gal plus a rehearsed resupply/boiling method. “Rehearsed” means performed once in peacetime, not merely described.
• A written Tier 4 resupply system names container set, vehicle plan, and distribution expectations; stored volume is treated as the bridge, not a 90-day stockpile.

What it needs from the owner

• Storage-location decision, especially for weight.
• Hands to fill, move, photograph, and rotate containers.
• A short peacetime rehearsal if the 42 gal + resupply/boil route is chosen.
• Per-item rulings on any container, filter, bladder, or treatment proposal after live prices are read.

Fences

• Food-grade containers only; no ex-chemical barrels and no old milk/juice jugs for long-term drinking storage.
• Tub water is non-drinking water unless separately treated under the sourced protocol; it is never counted as ready drinking water as-is.
• A filter does not override a Do Not Drink / Do Not Use notice, and no generic filter claim converts chemical water into safe water.
• Filtration is specified by contaminant class: the study’s Sawyer class addresses bacteria/protozoa, not viruses or chemicals.

W2 — WATTS

Objective. Build a tested backup-power layer for the owner-selected critical loads — Pavilion/Myth continuity or safe shutdown, device/AAC charging, refrigeration strategy if selected, and lights — while moving the household toward near-zero electricity dependence as duration grows.

What done looks like

• W0 produces the power census: generator existence or explicit UNKNOWN, fuel type/on hand if any, last run date and manual location if any, CO alarm and battery date, power banks counted by capacity, and battery needs counted by device.
• The owner names the protected-load list. No load is silently assumed critical; any powered medical equipment, if one exists, is sized first.
• Mathematics/Thermodynamics sizing is performed from the actual load list and measured or manufacturer-stated draw. The Oct study’s “about a day per 2 kWh charge for fridge + phones + lights + fans” is planning context only, not this house’s runtime claim.
• The installed posture passes an owner-run outage fixture: 1. selected loads transfer to backup without backfeeding; 2. Pavilion/Myth either stay inside their owner-set runtime objective or shut down cleanly; 3. phones/AAC charging works; 4. each adult and the shelter room has working battery light; 5. actual runtime or state-of-charge use is recorded against the prediction and the difference is printed.
• If refrigeration is protected, the load-shed plan states what is powered in brief windows and what is lived without.
• If a generator is part of the posture, its manual, fuel/rotation plan, outdoor placement, ≥20 ft separation, exhaust direction, and working CO alarm are all proven before it is counted.

What it needs from the owner

• Decisions: which loads matter, acceptable runtime, generator-versus-battery posture, and any circuit/transfer work by a qualified electrician.
• Hands for nameplate photographs, outlet/circuit facts, installation-day access, and the outage fixture.
• Money only through a live-priced, per-item proposal after sizing.

Fences

• No suicide cord or backfeeding, ever.
• No generator indoors, in a garage/basement, or under 20 ft from openings.
• No no-name/unlisted lithium station or loose salvaged-cell build as the family’s trusted power source.
• A generator, if any, is a bridge of days — not a 30-day plan — unless a sourced fuel and load calculation proves otherwise for this house.

W3 — RADIO REACH

Objective. Give the household a grid-free information and family-communications layer: receive official information first, then add two-way reach only through the owner’s separate rulings and licenses.

What done looks like

• Receive layer: a working battery/hand-crank NOAA-capable radio is counted, powered, tested on a live weather broadcast, and able to receive the local SAME alerting posture the owner configures.
• Official-information layer: utility and Polk County notice channels are identified and followed in peacetime; a printed contact card names who calls/texts whom, the out-of-area contact, meeting point, and cooling/shelter destinations.
• Mesh layer: this workstream consumes the pending LXMF ruling, OQ-104, exactly as ruled. It does not re-decide the stack, buy shape, vendor, or any D-2 device-role amendment. If OQ-104 authorizes hardware, the resulting nodes are configured for the lawful US posture named in that ruling and pass a two-node owner field fixture before they are counted as reach. If OQ-104 remains unruled or rules no purchase, this line remains GAP — ruling pending / not acquired, while the receive layer can still close.
• Voice layer: if the owner chooses GMRS, the owner files the FCC license himself; any radios are repeater-capable only if that is the approved proposal, and the pair passes a house-to-destination field check before it is counted.
• A local paper map is stored with the documents set.

What it needs from the owner

• OQ-104 ruling for mesh; no substitute decision is taken inside this charter.
• GMRS go/no-go and, if go, the owner’s own FCC filing.
• Hands for radio placement, alert configuration, and a short field check.
• Money only through live-priced proposals after the applicable ruling/license path is clear.

Fences

• No unlicensed transmitting.
• No EU-band LoRa hardware for US mesh use.
• Mesh expectations stay honest: text/telemetry class, terrain- and antenna-dependent; no voice/photo promise.
• A radio is not counted because it is in a box; it is counted when it powers, receives, and is heard by the owner in the fixture.

W4 — SOFTWARE FINISHES

Objective. Finish the four $0 software items the study and App Layer left open. Software is not the house’s main gap, but these four lines turn existing tools into proven resilience infrastructure.

W4.1 — Kiwix survives a Pavilion reboot

Done when: Kiwix is configured through a durable service/autostart mechanism rather than a one-session process; the Pavilion is rebooted in an owner-approved window; Kiwix returns without manual rescue; and a household device reads a real article locally afterward. The two-device reading half from APP-LAYER is completed as part of the same fixture where devices allow.

Owner needs: a reboot window and one phone/tablet for the read-back.
Fence: a process that is merely running today is not “survives reboot”; only the cold-reboot fixture proves it.

W4.2 — USB Lite resilience sticks

Done when: at least one write-once resilience stick is built from the study spec with the field guide, family comms plan/quick-cards, offline Polk/Central Florida maps, Kiwix reader path, and encrypted household-document copies selected by the owner; its manifest/checksums verify; and it opens offline on a clean device. Storage location and annual refresh date are recorded.

Owner needs: designate the stick(s), select which document copies may be encrypted onto them, and perform the clean-device opening.
Fences: a stick is never the sole copy of anything; sticks are stored in the house, not a hot car; the existing House Test Stick/App Vault does not satisfy this line unless the resilience contents and fixture are separately proven.

W4.3 — Offline phone map packs verified

Done when: the Florida map data named for the chosen offline app is downloaded in calm weather to each phone the owner designates for travel/evacuation, and each phone passes an airplane-mode fixture: find the house, a named cooling destination, a shelter/route destination, and the documents-container map reference without a network.

Owner needs: the designated phones in hand and storage space decisions.
Fence: “app installed” is not “maps in hand”; APP-LAYER records the Florida data as not in hand, and only the offline fixture closes it.

W4.4 — Kit-inventory app, after W0

Done when: after W0 supplies real household data, the APP-LAYER Part B app is built and proven as a local-first PWA with:

• capture-first inventory entries and append-only count history;
• tier checklist views that print met / short / unknown from inventory, never from a generic list’s opinion;
• days-of-cover timers with quantity, burn rate, arithmetic, provenance grade, and as-of date visible;
• expiry/rotation and staleness/GAP views;
• checksum-sealed local export and a printable paper view;
• a one-page data sheet and plain-language INSTRUCTIONS.md;
• fixture F-FP-1 passed, including the deliberate uncounted category printing unknown/GAP, never zero;
• Assayer proof and real household dogfood before any COMPLETE claim.

Owner needs: answer APP-LAYER §B.7’s open questions — whether a maintained paper/spreadsheet inventory already exists, household-entered settings, essential categories, tier targets, burn rates, and location labels — then dogfood the first real count.

Fences

• Local-only: no sync, analytics, accounts, or network requirement.
• The app records supplies, never people; nothing about Rin is recorded by the app.
• A stale count prints stale/GAP; the app must not animate a timer as though it were live truth.
• The build follows the house PWA, instructions, data-sheet, pre-update, Assayer, and dogfood gates. This charter sequences the build; it does not waive those gates.

Sequence note — source tension printed, not smoothed. APP-LAYER’s fixture design treats the app as the capture instrument for a first count. This owner commission instead puts the paper/owner-report W0 survey first and the app after W0 data exists. The charter follows the Nov 2 commission. F-FP-1 therefore remains an app-design fixture using a known test set; it does not replace the household’s W0 survey.

W5 — KIT & TOOLS

Objective. Disposition every remaining W0 GAP across Checklist §§2–12, in the Protocol’s binding order and with Rin’s §12 as a standalone first-class section.

What done looks like

Each line below is closed only by a dated count or owner decision, not by a purchase receipt alone:

• Food: T1 ~16,200 kcal and T2 ~37,800 kcal of shelf-stable foods the household actually eats; manual can opener counted; Rin-familiar foods stocked in depth as their own line; rotation begun.
• Sanitation: T1 bags/wipes/soap counted; T2 non-flush kit assembled and staged where the family would stay; T3 hygiene depth and a written waste-handling routine.
• Light: one working flashlight/lantern per adult plus the shelter room; spare batteries matched to actual device sizes.
• Heat/cooling: two cooling destinations named where possible, with route and fuel; the Day-3 above-90 °F decision point written into the household plan.
• Medical continuity: first-aid supplies counted; paper medication list held with documents; every daily medication’s days on hand and refill window established in the household’s own private inventory; at least a 7-day bridge proven or the shortfall printed as a GAP; longer buffers pursued early through prescriber/pharmacy channels.
• Cash: small-bills float counted by the owner’s chosen method; the amount is owner-held and is not printed in project records.
• Documents: IDs, insurance, medication list, contact card, plan, and filed survey gathered in one waterproof place; second/photographed offline set and full printed set completed by tier.
• Vehicle/fuel: each vehicle’s fuel and road-ready state recorded; hurricane-season no-empty habit and named-storm fill rule adopted by the owner; cooling-destination fuel included.
• Tools: only the tools W0 proves missing for the counted plan — starting with the manual can opener and the household’s own maintenance/shelter needs — are proposed. A tool is not bought to complete a generic list.
• Rin’s section (§12), paper/household record only:
• AAC device, charger, and dedicated charged power bank located;
• current printed communication board in two copies, existence/currency reported without photographing its content;
• familiar foods counted separately at her planning rate;
• named comfort item and familiar activity set located/staged;
• applicable supply classes counted with days of cover, with non-applicable classes marked N/A only by her parents’ word;
• fastest-breaking applicable class named;
• backup carer named in the illness/isolation protocol if the owner chooses to complete that T4 line, and whether it has been shared with that person recorded Y/N.

What it needs from the owner

• Location knowledge from both adults where a line depends on it.
• Hands for staging, printing, photographing non-sensitive shelves/labels, and rotation.
• Decisions on destinations, backup carer, cash posture, document set, and any item not to close.
• Pharmacy/prescriber conversations early, in peacetime, for medication buffers.
• Money only through live-priced, per-item proposals tied to a filed W0 GAP.

Fences

• No medication names/doses in shared project records.
• No single urgent in-event withdrawal is planned as the cash method; the float is built gradually in peacetime.
• No candles as the light plan.
• No food is counted for Rin merely because it is in the household total; her familiar-food line is counted separately.
• No purchase closes a line until the item is in hand, located, counted, and — where operation matters — tested.

7. Source tensions and evidence limits — printed, not smoothed

1. Maps: imperative versus state. The Oct 21 tech survey lists “Offline map packs staged on the phones” among BUILD items — an instruction to build, not proof of completion. APP-LAYER, seven days later, records CoMaps Florida data as ADOPTED-NOT-STOOD-UP, data NOT in hand, with the phone fixture owed. CLOSE THE GAP follows the later state record: maps are not done until W4.3’s offline fixture passes.
2. App sequence: spec path versus commission path. APP-LAYER designs the kit app as a capture-first instrument and its first fixture around performing a count in the app. The Nov 2 owner commission sequences the paper/owner-report survey first and the app only once W0 data exists. The charter follows the commission and prints the reversal; the app fixture remains a design test, not a substitute survey.
3. APP-LAYER is a dated state snapshot. Its Part A states are explicitly “as the records state it” on 2026-10-28. They are not silently carried forward as Nov 2 truth. In particular, its Setup B state/engine discussion is not used as a current-state source for this project; W4 uses only the App Layer’s Kiwix, maps, radio-absence, and app-spec lines, each still subject to W0/fixture re-proof.
4. Japan’s request does not reset house quantities. The Japanese request and the house Protocol use different water formulations and different local cases. The project takes the Japan request as the commission’s framing — ordinary households are being told to hold physical basics — while all sizing remains the Fallout Protocol’s Florida/Tier 2 arithmetic.
5. A purchase is not a capability. The study’s hunt list and Protocol Appendix A are proposal surfaces. An item closes a project line only when it is in hand, located, counted, and functionally tested where function matters.

Appendix A — OWNER-HUNT ground from the Oct 21 study

All prices in this appendix are STALE market ground as of Oct 21, 2026. They are not live prices, not quotes, and not buy recommendations. A future proposal must re-read the price live and receive the owner’s ruling per item.

Project note: W3 does not treat the Meshtastic row as a decision. OQ-104 governs the mesh/LXMF question. W2 does not treat the power rows as sized for this house until the protected-load list and draw are known.

Appendix B — Source map

• ~/workspace/fallout-protocol/CHECKLIST-2026-10-28.md — Act Zero AZ-1…AZ-14; §§1–12; tier quick reference.
• ~/workspace/fallout-protocol/FALLOUT-PROTOCOL-2026-10-28.md — headline Tier 2 conclusion; empirical spine; §§3–6 quantities and rules; §9 gaps/review proposal; Appendix A proposal fence.
• ~/workspace/fallout-protocol/APP-LAYER-2026-10-28.md — Part A have-list and named absences; Part B kit-app spec, data sheet, privacy line, and F-FP-1.
• ~/workspace/security-desk/resilience-field-guide.md — five local scenarios; sourced do/don’t lines; owner-input-needed block.
• ~/workspace/security-desk/resilience-tech-survey.md — BUILD / OWNER-HUNT / STUDY-MORE / NO classes; fleet conclusion; stale price ground as of Oct 21, 2026.
• ~/workspace/goals/doomsday-survival-tech/GOAL.md — goal of record.
• ~/workspace/goals/doomsday-survival-tech/files/ACT-ZERO-SURVEY-KIT-2026-11-02.md — W0 field instrument staged with this charter.

End of charter. Founding act complete; no workstream is marked started except W0’s kit, which is STAGED — NOT WALKED.