Shared Memory Hub

The crew's shared rules — one reference for Muse, Claude, and Gemini. Created Wednesday, November 4, 2026, at Robert's order. Updated every time a conversation sets or changes a standing rule; every change is dated in the Change Log at the bottom.

This hub holds only the rules everyone works under: shared ethics, FDC policy (public rules only), Florida law, state/federal law reference points, and Facebook/Meta policy. It is a public page — empire rules and public law/policy only. No personal, financial, family, health, employer-facility, or case details ever go in here.

A. Shared Ethics

The ethics screen (before anything posts — every piece, every time). Every piece passes two checks before it can publish: (1) the platform's current community guidelines, and (2) the FDC off-duty conduct pre-screen (Section B). A failed screen stages the piece and reports it the same day — it never posts, and it is never quietly fixed and posted.

Education only. Everything the empire publishes is education. No selling, no prices, no retailer links, no "for sale" or "where to buy" language — on any lane. The single exception is the Ko-fi tip jar. Brand disclaimers ride every post where they apply: finance lanes say "General info, not financial advice"; health lanes say "General health info"; legal lanes end "Education only, not legal advice"; cigar lanes say "Education only. Nothing for sale."

No static posts. Every post is a narrated video with word-for-word captions — no flat text or image posts anywhere in the empire.

Replace, then archive — never delete. A replacement goes live first; only then is the old version archived (YouTube Private, Facebook archive). Old posts are not deleted. (Two exceptions Robert ordered himself: retiring duplicate brand channels, and re-posting corrected pieces where he directed delete-and-repost.)

Quotes. Every quote must be real, from a real author, properly attributed, and verified against a reliable source before use. Never invented, altered, or misattributed. No Steve Jobs quotes, ever.

Sources and authors on every claim. Every study question, study guide, and researched claim carries its source and author(s) — a rule/statute citation for policy material, a named author and work for research material. Crew-authored practice or judgment with no external source is labeled as such, never presented as sourced fact.

Source Interest Rule. Material pulled from another account is used only if the subject is genuinely interesting — a real story or hook, visual potential, a notable name or fact, or a local angle. A dull or administrative source post is skipped with the reason logged, never mechanically converted.

Every tip carries its reason. Every tip published explains why it works and the problem it solves — never the tip alone.

Privacy rule (public pages). Public pages carry empire content only. Never publish personal, financial, family, health, or employer details, home addresses, or case specifics. If in doubt, leave it out.

Approvals discipline. Empire posts that are gate-certified are pre-approved by default under Robert's standing order (revocation phrase: "stop auto-approve"); standing holds are never covered by that approval. Everything else needs Robert's specific word: purchases, permanent deletions, email/message sends, Page creation, bio or name changes, and any account change — and anything money, legal, or irreversible. Small, reversible, low-stakes choices (privating or archiving a known duplicate, applying an already-prepped fix, tidying a stale record) are decided and executed by the crew and reported after the fact.

Firearms content. News, discussion, and education only. No links to sites that sell firearms or accessories, no "for sale" or "where to buy" language, no branded or sponsored firearms content, no prices. See Section E for the platform rules behind this.

Pre-publish quality gate. Nothing publishes without passing the quality gate (pacing, word-fit, quality, compliance). A failed gate stages the piece and reports — it never posts.

Two-Key Publishing (Nov 4, 2026). A gate-certified empire post publishes only when two keys are both on record: (1) Robert's approval — the blanket pre-approve line in his approval ledger or a specific approval he gave — and (2) Claude's signed pre-approval from his twice-daily officer pass (17:00 ET day-before, 12:00 ET top-up), which countersigns only what Robert has already OK'd after checking the holds list and the gate certificates by hash. Holds always win over both keys. A missing second key leaves the slot empty and reported — never silently filled. Scope is posts only: purchases, sends, deletions, Page creation, and account changes still need Robert's specific word. Revocation phrase stays "stop auto-approve." Full plan: two-key-publishing-plan-2026-11-04.md in the ai-handoff folder.

B. FDC Policy — Public Rules Only

This section is public rule material only — published Florida Administrative Code rules and Florida Statutes. No internal or non-public institutional information appears in any crew content, ever.

Employee code of conduct — FAC 33-208.002 / 33-208.003. The conduct rules apply on AND off duty. The points the crew screens against:

• No political activity on duty; no use of the position's authority in a partisan election; no state resources or state time for lobbying. (Fla. Stat. §104.31; §110.233(4)(b); §11.062)
• Never disclose or use non-public institutional information — no staffing, post assignments, schedules, security procedures, or incidents — in any post, letter, or content. (Fla. Stat. §112.313(8))
• No soliciting funds, petitions, signatures, or literature on agency property or while on duty. (FAC 33-208.002(21))
• "Conduct Unbecoming" — conduct that discredits the Department is disciplinable even off duty. (FAC 33-208.002(22))
• Candidacy for office while state-employed is barred, except local office with agency-head and department approval obtained first. (Fla. Stat. §110.233(4)(b))
• Appearing before the Legislature during agency business hours must be on approved leave or an off day, in civilian clothes, by personal vehicle, recorded in citizen or union-member capacity. (Fla. Stat. §11.061)

Pre-send policy check. Before anything FDC-related is sent or published, the content is checked against FDC policy and procedure, the employee code of conduct (FAC 33-208.002/.003), and facility rules. Content stays public rule/procedure and public news only. Anything that fails does not send, and the failure is reported to Robert instead.

No FDC leadership contact — ever. The crew never reaches out to, or drafts messages to, any administrator in Robert's chain of command. Advocacy targets are elected officials, the Governor's office, the Department of Management Services, the Legislature, and the union — never his own leadership.

Justice Blueprint scope. The channel covers Florida law and law enforcement in general — Florida law, courts, statutes, how the system works. Nothing agency-specific, nothing corrections-specific, nothing about Robert's job. Textbook altitude only; every piece ends "Education only, not legal advice."

Union activity is protected. Union/PBA activity is affirmatively protected under Florida Statutes Chapter 447; §447.501 bars agency interference with or retaliation for it. Advocacy runs through citizen and union channels, on personal time and personal accounts.

Public rule references the crew studies (one-line summaries, public rules only):

• FAC 33-602.210 (Use of Force): force is authorized only for the purposes in Fla. Stat. §944.35(1)(a); organized force is planned control/escort/relocation, reactionary force is immediate force to stop violence or resistance; force is a last resort, must cease on compliance, and is never punishment.
• FAC 33-404 (Mental Health): five levels of care — Outpatient, Infirmary, Transitional, Crisis Stabilization, and Corrections Mental Health Treatment Facility Care — with placement by adaptive functioning and treatment need, and an individualized services plan for every inmate receiving services.

C. Florida Law

General information only — not legal advice. These are the consumer-law references the empire's Florida consumer lane actually teaches, each with its statute cite.

• FDUTPA — Fla. Stat. §501.204(1): unfair or deceptive acts or practices in trade or commerce are unlawful.
• Private right of action — §501.211(2): a person who has suffered a loss from a §501.204 violation may recover actual damages.
• Attorney's fees — §501.2105: the prevailing party in FDUTPA litigation may recover reasonable attorney's fees and court costs.
• Home Solicitation Sales — Fla. Stat. ch. 501.021–501.055: for most sales over $25 made away from the seller's main place of business (for example, signed at the buyer's home), the buyer may cancel in writing by midnight of the third business day after signing; a mailed notice counts from postmark. Under §501.031, the seller must give the buyer written notice of the right to cancel ("Buyer's Right to Cancel"), and if the buyer cancels, the seller may not keep any cash down payment.
• Gift certificates — §501.95(2)(a): a gift certificate purchased, or credit memo issued, in Florida may not have an expiration date or any post-sale charge or fee (including service, dormancy, account-maintenance, or cash-out fees). Exceptions exist for charitable, employee-incentive, loyalty, and promotional certificates given without a separate charge, and for bank-issued cards redeemable by multiple unaffiliated merchants, which follow federal rules.
• Motor vehicle repair — §559.920(13) and §559.921(1): part of Florida's Motor Vehicle Repair Act provisions on unlawful acts by repair shops and the enforcement/remedy framework that follows from them.

D. State Law — Federal Reference Points

Reference summaries of the federal provisions the crew's dispute and consumer work actually uses. This section grows only as Robert adds topics — nothing is padded in.

Fair Credit Billing Act (FCBA) basics:

• 15 U.S.C. §1666(b)(3) and 12 CFR 1026.13(a)(3): certain billing errors — including goods or services not accepted by the consumer or not delivered as agreed — can be disputed with the card issuer.
• 15 U.S.C. §1666(a): on a proper billing-error notice, the issuer must acknowledge within 30 days and resolve within two billing cycles (no more than 90 days).
• 15 U.S.C. §1666i and 12 CFR 1026.12(c): a cardholder may assert claims and defenses arising from a transaction against the card issuer, subject to the statute's conditions.
• 15 U.S.C. §1666a: governs creditor reporting of disputed amounts while a billing-error claim is open.
• Rigby v. FIA Card Services, 490 F. App'x 230 (11th Cir. 2012): Eleventh Circuit authority the crew's dispute work cites on an issuer's duty to actually investigate the documents provided before deciding a claim.

E. Facebook / Meta Policy

Working summary from the platform guidelines quick-reference compiled October 10, 2026 (sources: Meta Community Standards and YouTube Help Center), with the October 11, 2026 Reels addendum and the October 15, 2026 ethics-gate addendum. The full file lives with the crew's compliance records; this is the summary everyone works from.

Community Standards basics the lanes follow. No hate speech, harassment, threats, graphic violence, nudity, misinformation, spam, or fake engagement. Content must be original — Pages that primarily repost unoriginal content get reduced distribution and demonetization under Meta's 2026 original-content rules; content must be produced by the Page owner or add meaningful new value (fresh analysis, new information).

Page policies. No misleading claims — titles and packaging must match what the content actually delivers. Education framing governs every lane (see the disclaimers in Section A). Posting pace stays human and consistent, never spammy.

Reels rules. No watermarked content from other platforms (a TikTok watermark gets downranked — always upload the clean master, never a re-export). Original or licensed audio only; audio from Facebook's own library is fine. No engagement bait in captions ("share if you agree" reduces reach). Reels under 90 seconds get the most distribution; hook in the first 2 seconds.

Firearms on Meta. Facebook restricts firearms sales — no buy/sell posts, no private-sale listings. Discussion, news, and education about firearms are allowed on Pages. The crew goes further (Section A): no sales links or retailer links at all.

Monetization. Facebook Stars requires 500 followers held for 30 days. A payout account must be set up within 6 months of first earning or the earnings are lost. Clean, no-watermark masters are produced per platform.

YouTube platform policy (the empire publishes there too). From the same compiled guidelines: no content intended to sell firearms or accessories and no links to sites that sell them; no firearms manufacturing or conversion instructions; branded or sponsored content featuring weapons or ammunition is prohibited (YouTube policy, September 2026) — never check the paid-promotion box on firearms content. AI-generated or altered content that is realistic must be disclosed at upload. Finance and health content stays general information with its disclaimer — no personalized advice, no guaranteed returns, no medical advice or promised results.

AI-content labeling. Where a platform requires an AI-generated-content label (TikTok offers/requires it on upload; YouTube requires altered-content disclosure for realistic AI content), the label is set — always.

G. Content Protections — Create Without Getting Sued or Flagged

These rules govern every piece on every lane. They exist so the empire can publish about brands, people, and events without trademark claims, copyright strikes, defamation exposure, or platform flags.

Trademark — nominative fair use. A brand name may be used IN WORDS to identify and discuss that brand — history, education, review, news. That is lawful nominative use, and it is the only way brand names appear here. Never: a brand's logo or logo-style mark, its slogans, its trade dress, or its styling used as decoration or as branding for our pages. Never imply sponsorship, affiliation, or endorsement by any brand. Where a brand is the subject of a piece, the page carries the line "Education only — not affiliated." A brand name is never used to sell anything.

Copyright. Original artwork and original narration only. No clips, photos, footage, ad creative, or music from brands, leagues, studios, or other creators without a license or clear public-domain status. Public-domain and openly licensed sources are preferred and are cited. Quotations are short, real, verified, and attributed (the Section A quote rule). No song lyrics beyond a brief credited line. Team and league footage is never used — describe it, draw it, don't lift it.

People and likeness. Athletes, founders, and other public figures may be named and discussed editorially — news and education. No fake quotes. No invented endorsements. Nothing that implies a person endorses our page or any product. Private individuals are not named in negative stories.

Defamation shield. Every factual claim about a person or business is verified at a real source BEFORE scripting, and the source is recorded in the piece's sidecar. Where sources disagree, the script states only what the strongest source confirms — the Air Ship rule: state what the document confirms, not the legend. Opinions are framed as opinions. A claim we cannot verify does not run.

Platform-flag protections. No engagement bait — no "like / share / comment or else" mechanics. No misleading titles or thumbnails: the title must match the content. AI-content labels are set wherever the platform requires them (Section E). No repeated or duplicate uploads across pages. Firearms stay news and education only — no prices, no retailer links, no sales facilitation (Sections A and E). No graphic violence imagery. No medical or financial advice claims: lanes that touch law, money, or health run education framing with the not-advice line (Section A).

Pre-publish protection check. Run alongside the existing gates, one line each: name in words only? No logos or slogans? Sources recorded? No lifted media? No prices or sales links on education lanes? Title matches content? If any answer is wrong, the piece stages and is reported — it does not post.

H. Kits Registry — Coding, Deployment, and Operations

A "kit" is a packaged bundle — setup script(s) + protocol doc + checklist — so any seat can install or run it the same way. (The model is Claude's GitHub Publisher Kit.) Registry rules:

• A kit is marked LIVE only after it has run end-to-end once.
• Status changes get a dated line in the Change Log (Section F).

• New kit ideas enter as QUEUED with a named owner before anyone builds.

• Publisher Kit — the Alienware single-publisher service + deploy keys; every GitHub push runs through it, card-free. Owner: Claude (Alienware). Status: BUILT — awaiting Robert's one-click install on the Alienware.

• Deploy Key Kit — one-click Ed25519 keypair generation for a new machine/repo, the registration checklist, and the fingerprint verification step. Owner: Muse. Status: LIVE Nov 4 — Muse's "Muse empire deploy" key is registered on the website repo and verified Nov 4, 2026: git ls-remote over ssh.github.com:443 succeeds (HEAD 74ce92f9). A second key ("alienware-empire-deploy") is also registered.
• Pre-Approval Officer Kit — Claude's twice-daily two-key check: candidate list in, signed pre-approval ledger entries out. Owner: Claude. Status: BUILT Nov 4 — work order delivered; first officer pass due 17:00 ET Nov 4; entries provisional until Claude's signing key exists.
• Sign & Encrypt Kit — crew note signing (Ed25519, .sig sidecars, allowed-signers registry) + age encryption for BANKING files only. Owner: Muse. Status: LIVE Nov 4 for Muse's seat; Claude/Gemini key registration pending.
• Gate & Certification Kit — gate_fast / gate_verify + motion check + build-in-progress guard, packaged so any new lane or machine certifies pieces identically. Owner: Muse. Status: LIVE (in daily use); packaging for Alienware install QUEUED.
• New Lane Launch Kit — launch a Page/channel in one pass: artwork templates, bio pattern, state file, topic-bank scaffold, wave wiring, crew registry updates. Codified from the Nov 4 Shoe Education + Shoe University launch. Owner: Muse. Status: QUEUED (build from the Nov 4 launch record).
• Restart-Proof Production Kit — production jobs write checkpoints (script done / render done / gate done / post done) so a runtime restart RESUMES a build instead of killing it; created after the Nov 4 restart killed two shoe-reel jobs mid-render. Owner: Muse + Claude. Status: QUEUED — highest priority after the Publisher Kit install.
• Bridge Health Kit — hub/queue/webhook probes, bridge_state publish, battery block, watchdog; one-screen status. Owner: Claude. Status: PARTIAL — probes + state publisher live; watchdog from the redundancy plan not yet built.
• Mailbox Courier Kit — standard crew-note format, watermarks, message IDs + ACKs across the four bridge lanes (Instant Hub / Drive / GitHub mirror / SSH spooler). Owner: Muse + Claude. Status: PARTIAL — Drive lane + watermarks live; ID+ACK from the Nov 3 redundancy plan not yet built.
• Site Publish Kit — publish-empire.sh (git push) + connector snapshot fallback + blob readback verification as one tool for every empire page (hub, topics, shared memory, AI sync). Owner: Muse. Status: LIVE on both routes — the git route's deploy key verified Nov 4, 2026 and the end-to-end push test PASSED the same evening (publish-empire.sh push, commit 058f7ac). Switching the four site-publish jobs to publish-empire.sh is the remaining step.
• Backup & Recovery Kit — encrypted (restic/age) backups of the bridge, staged-pool manifests, and job definitions, with a restore runbook for VM replacement. Owner: Claude. Status: QUEUED.
• Secrets Kit — tokens/config as age-encrypted files inside the private bridge repo, unlocked per machine; ends loose token text files. Owner: Muse + Claude. Status: QUEUED (depends on Sign & Encrypt Kit key registration completing).

I. Auto-Approval Charter — Stop Reviewing Everything

Set by Robert, Nov 4, 2026. Full text: auto-approval-charter-2026-11-04.md in the ai-handoff folder.

• Classes, not items. Robert approves classes of work once, in advance. Actions inside a class run without asking; his review is after the fact, in the digests and logs.
• Four mechanisms: (1) empire site publishes go by git push with deploy keys — no connector approval cards (repo deploy key verified Nov 4, 2026 and the end-to-end push test passed that evening, commit 058f7ac; switching the four site-publish jobs to the git route is still owed); (2) two-key extended — Claude's daily officer pass now also issues class entries for Drive mailbox uploads and site publishes, alongside post pre-approvals; (3) reversible = automatic — archive, private, move, schedule, stage, upload a copy, and log writes never need an ask, empire-wide, inside a job's written scope; (4) opt-out digest — the 5:05 PM digest lists tomorrow's plan as approved by default; Robert replies only to veto, and vetoes are recorded in approval-vetoes.jsonl and converted to ledger holds that override any blanket approval.
• Never automatic: purchases/payments, permanent deletions, emails or messages sent to real people, Page/channel creation, bio/name/account/security changes, money movement, legal or government submissions, and every standing hold. Those need Robert's specific word every time.
• Kill switches: "stop auto-approve" revokes post pre-approval; "stop the charter" revokes the whole charter; a named hold in chat overrides any class at any time.

F. Change Log

• 2026-11-04 — Hub created at Robert's order (Nov 4, 2026): "Make a hub for shared memory and update it every time we talk." First edition carries the shared ethics screen, FDC policy (public rules only), Florida law, federal reference points, and Facebook/Meta policy. From now on, whenever a conversation sets or changes a standing rule, this hub is updated the same day and the change is logged here.
• 2026-11-04 — Section G (Content Protections) added at Robert's order: "Put in protections in the hub to create content in a way that im not sued or flagged." Trademark (nominative fair use — brand names in words only, never logos, slogans, or implied endorsement), copyright (original work only, no lifted media), people and likeness, the defamation shield, platform-flag protections, and the pre-publish protection check now govern every lane.
• 2026-11-04 — Two-Key Publishing added to Section A at Robert's order ("have claude pre approve what i already say is ok" → "Build it"): Robert's recorded approval + Claude's signed pre-approval + a valid gate certificate are all required before a post publishes; holds override; scope is posts only. Full plan in the ai-handoff folder (two-key-publishing-plan-2026-11-04.md).
• 2026-11-04 — Section H (Kits Registry) added at Robert's order: "think of more kits we can make to make everything run better and add to the hub for coding and deployment." Twelve kits registered with owners and true current statuses — Publisher, Deploy Key, Pre-Approval Officer, Sign & Encrypt, Gate & Certification, New Lane Launch, Restart-Proof Production, Bridge Health, Mailbox Courier, Site Publish, Backup & Recovery, and Secrets. Registry rule set: a kit is LIVE only after one end-to-end run; status changes are logged here; new ideas enter as QUEUED with an owner.
• 2026-11-04 — Section I (Auto-Approval Charter) added at Robert's order: "figure out a way to stop having me review everything… Build it now." Robert approved the 1+2+4+6 package: git-route publishing, two-key extended to Drive uploads and site publishes, reversible = automatic, and the opt-out (veto-only) 5 PM digest. Charter file in the ai-handoff folder; veto ledger live; Claude's extension addendum delivered the same day. The git route's transport is fixed (SSH over port 443); activation waits on the repo deploy key verifying.
• 2026-11-04 (evening, crew sync block) — Deploy key verified: GitHub's Nov 4 emails confirm two deploy keys on the website repo ("Muse empire deploy" and "alienware-empire-deploy"), and Muse's git ls-remote over ssh.github.com:443 now succeeds (HEAD 74ce92f9). Kits Registry updated (Deploy Key Kit LIVE; Site Publish Kit git route verified, end-to-end push test + job switch still owed). New properties registered: Facebook Pages Shoe Education and Shoe University launched Nov 4, 2026 and wired into the daily Facebook waves — 11 Pages total in the waves. End-to-end git push test passed later the same evening (publish-empire.sh, commit 058f7ac).

Sources for this hub: Robert's standing records (MEMORY.md), the platform guidelines quick-reference compiled October 10, 2026 (with October 11 and October 15, 2026 addenda), the FDC ethics pre-screen built October 15, 2026 from the verified October 14, 2026 ethics audit, the sergeant study guides (public FAC rule text), and the Florida Consumer lane's verified statute records.