A running public record of what we promised, what we delivered, what we missed, and what we learned. We write it because most projects quietly rewrite their roadmaps. We won't.
Every public promise the Federation makes gets a row on this page. When we keep it, we mark it KEPT. When we miss a deadline, we mark it DELAYED with the reason. When we fail, we mark it MISSED and write what we learned. When priorities change and we cancel something, we mark it CANCELLED with the explanation.
Entries are never deleted. If you see a past roadmap item that didn't ship, it will be here with a clear status. If we get something wrong that's publicly visible, the correction appears here before we fix it. This page is longer than our project is old, and it always will be — because being trustworthy means documenting the misses, not hiding them.
Of 8 commitments that have been resolved, 8 are KEPT, 0 are MISSED, 0 are CANCELLED. The remaining 13 entries are ON TRACK — forward-looking commitments not yet resolvable.
One historical commitment — #H009 (Research Log cadence) — was filed as DELAYED after a Week 03 / Week 04 miss, then recovered to KEPT with the combined catch-up post for Week 05. The original DELAYED state is preserved in the entry. The slip itself was logged, which is the discipline.
Method: resolved commitments = entries with status KEPT, MISSED, or CANCELLED. ON TRACK entries are pending and excluded from the rate. Recovered entries (DELAYED → KEPT) count as KEPT in the current rate; the original DELAYED state remains visible in the entry. Updated manually with the stats strip on every deploy that adds or resolves an entry.
Promises we've made publicly — on the site, in Telegram, on X, or in published writing — that we are still working to deliver.
Before launch, the federation committed to locking 10% of total supply across 3 separate Streamflow contracts. The lock contracts are on-chain and immutable. This promise is verifiable in real time on the treasury page.
Status: Kept from day one. The three contracts are live. Balances are readable by anyone from Solana RPC.
When the first Streamflow unlock event occurs, the released tokens will not be sold into the market. They will either be re-locked, rotated into operational treasury (visible on-chain), or used per a specific, pre-announced purpose. This will be verifiable on-chain both before and after the event.
Status: Commitment standing. Will be tested at the next unlock — see countdown on /treasury. If we break this, it will appear as MISSED on this page before any other coverage.
Per Moonshot's standard launchpad mechanics, when $GFOF reaches $73K market cap, the token migrates to Raydium. Mint and freeze authorities are revoked automatically as part of the migration. The federation has publicly stated this path since launch.
Status: In flight. This is a mechanical trigger, not a team-controlled event — it happens when the market cap is reached. If the bond is not reached and the project winds down, this will be documented here as a cancelled commitment, not silently forgotten.
The federation has committed to launching on-chain governance via the Realms platform within 60 days of reaching the bond. Holders will have real voting weight on treasury allocation, staking parameters, and protocol direction.
Status: Prerequisite (bond) is still in flight. Advisory polls are being run in Telegram before the formal DAO launches so there's a record of honored community decisions from before vote weight kicks in.
A substantive monthly publication — DeFi trend analysis, protocol teardowns, security issues in our space. Free. No paywall. Published as both a PDF and a pinned X thread.
Status: First issue in preparation. If a scheduled issue ships more than 7 days late, it will be marked DELAYED with the reason. If we skip a month entirely, it will be marked MISSED.
Before writing any smart contract code for the lending protocol, the federation publishes a public design spec for borrower-protective liquidation. The spec is open to public criticism, and its revisions will be tracked here.
Status: v0.2 of the spec is live at /liquidation-spec (v0.1 published 2026-04-20, v0.2 published 2026-04-21 adding Section 7 on non-standard collateral types). Revisions are versioned. Each revision's diff is documented in the spec's own revision log and as a corrections entry below.
The federation has paused paid KOL campaigns and paid promotional spend pending a return of macro liquidity. This commitment is not about the pause itself — it is about the conditions under which the pause ends.
Before any paid promotional spend resumes, the federation commits to publishing a written set of market signals that must be met. The trigger will live on this page. Loosening it — firing the trigger earlier than the published thresholds would allow — requires a minimum 14-day waiting period with the change logged here as a public amendment before any spend occurs. Tightening the trigger (delaying spend further) is unconstrained and does not require a waiting period.
First-draft framework (v1, subject to one round of refinement before activation):
A 3-of-4 threshold. At least three of the following four conditions must be met before paid spend resumes:
Rationale: The risk being addressed is firing paid spend too early on vibes — deploying runway into a dry market where paid impressions don't convert. A written trigger, published externally, creates a pre-commitment against that impulse. The 3-of-4 threshold allows for conditions where macro lags one indicator but the other three have turned clearly constructive. The 14-day loosening-only waiting period prevents same-week revision of the trigger to justify spending that was already decided emotionally.
Acknowledged failure mode: If the trigger is set too strict, we miss the first leg of a liquidity return while waiting for confirmation. The loosening-with-waiting-period provision is the release valve for that case — it allows amendment, but forces the amendment to be made 14 days before any spend, in public, with reasoning. This is intentionally uncomfortable.
Status: Framework published 2026-04-21. Subject to one round of refinement before activation — community feedback via Telegram or /security channel. Confirmed version will be marked v1.0 here. Once marked v1.0, the commitment is binding under the amendment rules above.
Revised 2026-05-05: The original commitment named "Medium and Mirror" as cross-post surfaces. Mirror.xyz consolidated into Paragraph in late 2025 and no longer exists as a separate publishing platform. The commitment is hereby revised to Medium only. See #H008 for the full correction record.
The Federation Research Log publishes weekly on Paragraph (commitment #H005). Beginning with Week 03 (due 2026-05-06), each issue is also cross-posted to Medium within 24 hours of Paragraph publication, with a clearly stated canonical link back to the Paragraph original.
The cross-post is not new writing — it is the same essay, distributed to an additional surface. Paragraph remains the source of record. The cross-post exists so the work meets readers where they already read, without diluting the canonical archive.
Tracking: KEPT each week if the Medium cross-post is published within 24 hours of the Paragraph original. DELAYED if delayed beyond 48 hours, with reason logged. MISSED if a week is skipped without a public reason recorded here.
Status: Commitment standing. First test: Week 03, due 2026-05-06.
The Federation will hold Office Hours monthly in the Telegram community (t.me/GFOF_SOL). Format: third Wednesday of each month at 2 PM EST / 7 PM UTC. Duration: 30–45 minutes maximum. The session is pre-announced seven days prior on @GFOF_Offcial and pinned in Telegram twenty-four hours prior. A transcript or recording is published within 48 hours of completion.
Office Hours is substantive Q&A only — not a hype event, not a price discussion, not a roadmap announcement venue. Voss-voiced opening and closing transmissions; founder voice for the Q&A itself. Off-topic questions (price predictions, financial advice, unrelated crypto) are politely declined and the floor moves on.
Inaugural session: Wednesday, May 21, 2026 at 2 PM EST / 7 PM UTC.
Tracking: KEPT each month if the session is held within the announced window and archived within 48 hours. DELAYED if held but archived late, with reason logged. MISSED if cancelled or postponed without 48-hour advance notice. CANCELLED if the practice is discontinued, with public explanation.
Status: Commitment standing. First test: 2026-05-21.
The 2–4 originated posts per week rule on @GFOF_Offcial remains unchanged. Alongside that rule, the Federation now engages substantively with the broader DeFi conversation on a daily cadence: replies to substantive DeFi research threads, retweets-with-comment of relevant analytical work from credible accounts, and replies to mentions of the Federation account.
The engagement window is bounded: approximately 5–15 minutes per day, replies on substantive threads only. No promotional commentary. No engagement-bait. No shilling. Casual Federation voice is acceptable for this activity; Voss voice remains reserved for substantive Federation declarations and Office Hours opening/closing.
This commitment exists to clarify what was previously ambiguous in the original posting cadence rule (#H007). Engaging with the broader DeFi conversation is on-brand even when the originated-post cadence stays disciplined.
Tracking: KEPT each week if engagement occurred at least 5 of 7 days. DELAYED if a single week dips below 3 days without a stated reason. MISSED if engagement is absent for 3 or more consecutive days without a stated reason. CANCELLED if the practice is discontinued, with public explanation.
Off-limits, restated: Volume bots, paid KOL spend (paused under #007), hype framing, urgency framing around bond, simulated activity, daily originated posts on @GFOF_Offcial, raid coordination. None of these are permitted under this commitment.
Status: Commitment standing. Begins 2026-05-05.
The Galactic Federation operates products. The first operational product is Dossier — the Federation's intelligence arm, a smart-money convergence detector for Solana, live at dossiertrack.co. Dossier has independent branding and pricing, but it operates inside the Federation's structural commitments. One of those commitments is that revenue flows back.
Dossier has committed publicly (see Dossier Corrections #006) to deploying a staged percentage of its net revenue directly into $GFOF/SOL liquidity on Raydium, quarterly, with on-chain transaction proof. The schedule:
Phase 1 — Beta period (now through ~Aug 2026): no revenue, no contribution.
Phase 2 — Paid launch through first $5K MRR: 25% of Dossier net revenue → Raydium LP, quarterly.
Phase 3 — $5K MRR sustained two consecutive quarters: steps up to 50% of net revenue → Raydium LP, same quarterly cadence.
Dossier Treasury Wallet: G1MLNThNPE8hcZQfNTcjZGEDaSx1otutcNScLazBc92Y ↗ (verifiable on Solscan)
Mechanism: Stripe payouts → dedicated treasury wallet → quarterly conversion → addition to $GFOF/SOL Raydium LP. LP receipt permanently held by Dossier Treasury. Quarterly injection details appended to Dossier Corrections #006 with transaction signatures verifiable on Solscan.
This is not a marketing promise. It is a structural commitment from a Federation operation back into Federation liquidity. The Galactic Federation does not extract value from its operations — its operations feed it. Dossier is the first such operation. Future Federation operations will follow the same pattern, with each commitment logged here and on the operation's own corrections log.
Status: Phase 1 (pre-revenue, beta). First obligated contribution begins on Dossier paid launch. Phase transitions and quarterly injection details will be appended to this entry as they occur — never deleted, never edited retroactively.
The Federation's value rests on records that are verifiable now and later. Every verifiable record inherits the security assumptions of the cryptographic layer beneath it. Stating those assumptions in the open is itself a transparency deliverable. This entry logs that commitment formally.
What the Federation commits to:
1. A cryptographic-dependency inventory — a plain-language map of which Federation transparency artifacts are hash-durable versus signature-exposed. The inaugural inventory is published as Federation Research Log Week 06 (Paragraph, canonical).
2. Tracking NIST and Solana-ecosystem post-quantum developments on the existing research cadence (#H005) — not a separate workstream.
3. Trigger-based re-evaluation, not dates: (a) Anza/Firedancer shipping protocol-level post-quantum cryptography on Solana; (b) a credible, dated forecast of a cryptographically-relevant quantum computer; (c) NIST finalizing FN-DSA or a signature scheme materially better suited to Solana's constraints. Reaching a trigger obligates a documented re-assessment here — nothing automatic.
4. A standing anti-claim: the Federation will not market quantum resistance, will not display a "quantum-secured" badge, and will not adopt QFS / "quantum finance" narrative framing.
The anti-claim is the binding part. If the Federation ever publishes a quantum-security claim, that is by definition a corrections-log event and should be treated with the skepticism this rule exists to earn. The public statement of this posture lives in the FAQ; the constructive demonstration is the Week 06 inventory.
Trigger status at filing: Trigger (a) partially activated 2026-04-27 — Anza and Firedancer publicly converged on Falcon and published prototype implementations. It did not fully fire: per Jump Crypto's own technical write-up, this "does not amount to adopting Falcon as a new protocol-level signature scheme." The obligation imposed (a documented re-assessment) was met in the Week 06 post. No Federation action is obligated, because the trigger condition — protocol-level shipping — has not been met. Recorded here so the framework's first real test is on the log, not just in the research post.
Status: Standing commitment, active. Reviewed on the research cadence. This entry is appended, never edited retroactively; trigger activations and re-assessments are added here as they occur.
On 2026-05-19, an additional 30,000,000 $GFOF from team-controlled treasury were committed to a new Streamflow lock contract — a 4th immutable contract supplementing the existing 3 (#001). Recipient: project treasury wallet. Full cliff release: 2028-05-31. Contract address: Fi2bBhWjU8j5W9orTfzrQi3QyTGgY8RFkmzKogeHnJ5x.
New locked total: 130M $GFOF (13% of total supply) across 4 Streamflow contracts. Verifiable on-chain on the treasury page and on Solscan.
Tokenomics figure update. The previous public breakdown of 80% community/liquidity, 10% rewards/reserve, 10% dev rounded team-held treasury tokens into the community/liquidity bucket. The new lock moves 30M of those team-held tokens explicitly into the locked-dev column. Site copy is updated this deploy to reflect on-chain reality: 77% community/liquidity, 10% rewards/reserve, 13% dev locked. The original 10%-dev / 100M / 3-contract claim was accurate for the previously-locked portion (verified individually: Lock 1 30M, Lock 2 30M, Lock 3 40M); this entry documents the expansion to 130M / 4 contracts and the more precise breakdown going forward.
Why now: non-circulation discipline. Tokens under team control that could theoretically be moved are now contractually immobilized until 2028-05-31. Capital follows discipline, not noise.
Status: Standing commitment, active. The 130M remains locked until the earliest scheduled unlock event — see /treasury for the full timeline. This entry is appended, not edited retroactively. If any of the 4 contracts is ever cancelled, accelerated, or otherwise modified, that change will appear here as a separate, appended status update.
On 2026-05-19, in the bond-trigger commitment thread published from @GFOF_Offcial (cross-posted to Telegram and to Week 07 of the Federation Research Log), the Federation publicly committed to initiating formal audit engagement immediately upon $73K bond completion. The engagement covers any deployed contract code before activation.
The commitment is to the engagement process, not to a finished audit by any specific date or by any specific firm. Audit firms have been researched but will not be named publicly until findings are delivered and published. This avoids the common DeFi pattern of "audited by X" claims made before findings exist.
What activates at trigger: the engagement process begins immediately; the bug bounty scope (currently on /security at $50–$500 per verified finding) expands to cover all newly-deployed contracts; when findings deliver, they are published in full — including findings inconvenient to the project.
What is NOT committed: a finished audit by date X, a named firm, an audit cost, or an audit duration. These are outside the team's unilateral control. Committing to events outside our control would be the kind of overcommitment the corrections log exists to catch.
Status: Standing commitment, ON TRACK pending bond. This entry is appended, never edited retroactively. When engagement begins, a status update will be appended below. When findings are published, those publications will be linked back from this entry.
On 2026-05-26, the Federation published a structural position in Week 08 of the Research Log — "Why the Federation Is Not Pursuing a Buyback-and-Burn" — stating that no buyback-and-burn program is being pursued at this time.
The position is conditional. The Federation would revisit a buyback-and-burn if all four of the following materialize:
The Federation's existing value-return mechanism is the Dossier net revenue loop to the $GFOF/SOL Raydium LP per #011. The Week 08 entry explains why a revenue-routed liquidity reinforcement mechanism is structurally different from — and arguably better suited to the Federation's discipline framework than — a buyback-and-burn.
Status: Standing position, active. If the conditions described in Week 08 materially change, that change will be documented here as an appended status update. If the Federation ever does pursue a buyback-and-burn, the rationale and the changed conditions will be filed as a new corrections entry referencing this one. This entry is appended, never edited retroactively.
On 2026-05-26, the Federation published Governance Specification v0.1 — a complete design for the $GFOF DAO on Realms — before deploying any governance infrastructure. This applies the spec-before-code discipline to governance, the same way /liquidation-spec applies it to the lending mechanism.
The commitment: all governance parameters (proposal threshold, quorum, approval thresholds, voting periods, execution timelock) are proposed as v0.1 draft-for-comment, not committed. A public comment period is open. Parameters are refined into v0.2 in response to comment, and ratified by the first on-chain governance vote — not set unilaterally. The DAO does not deploy until after the $73K bond completes.
Two structural decisions documented in the spec: (1) the 13% locked dev allocation does not participate in governance voting — locked-for-discipline does not double as locked-for-control; (2) an explicit list of what governance cannot do, placing the corrections log, correction #007, correction #012, correction #003, the locked dev tokens, and the revoked mint/freeze authorities permanently outside governance scope. These constraints cannot be changed by any vote, standard or constitutional.
Status: Standing commitment, active. Comment period open. v0.2 will be published incorporating feedback. DAO deployment is post-bond per the stated sequence. Any deviation from this sequence will be documented here. This entry is appended, never edited retroactively.
Commitments that have been resolved one way or another. These entries are permanent. We do not edit or remove them, only append corrections.
Before launch, the federation committed to a quiet start: no paid KOL campaigns, no influencer allocations, no roadmap items promised without a clear path to delivery.
Resolution: Kept. Launch was organic. No KOL checks have been cut. Roadmap items are documented on this page as specific commitments with status, not as generic future promises.
The federation publicly committed that before any lending-product trust ask, we would ship a live transparency page that reads directly from Solana.
Resolution: Kept. /treasury shipped v1 on 2026-04-19, extended on 2026-04-20 with the Unlock Early-Warning System. All numbers are read from the chain in the visitor's browser — not served from our server.
When v0.1 of the liquidation spec was published on 2026-04-20, the federation committed to substantive iteration rather than the more common pattern of publishing a design doc once and never revisiting it.
Resolution: Kept. v0.2 published 2026-04-21, adding Section 7 on non-standard collateral types — connecting the existing mechanism to the broader DeFi capital-efficiency conversation. No mechanism changes from v0.1; framing addition only. Full diff in the revision log on the spec page.
The federation built a series of disciplined surfaces across 2026-04 — the liquidation spec, the treasury page, this corrections log, the security policy, and the server-side chatbot prompt (hardened in v16 against citing undocumented features). The home page, however, still carried older marketing patterns that contradicted that discipline: a "Federation Points System" with specific 500/750/250 point values and a promise that points would "convert to $GFOF allocations"; a staking section presenting 1.5×/2×/3× multipliers and a "20% APY base" projection as though the numbers were committed; Founding Member NFT benefits listed as concrete ("+0.5× staking, 2× governance vote, 2× raffle entries"); a Stake2Earn roadmap item with a specific mechanism ("top holders earn SOL from trading fees"); and two client-side chatbot widgets (home + app) that embedded their own system prompts with phantom-feature claims separate from the disciplined server-side prompt.
Resolution: Kept. Home page updated on 2026-04-21 as part of the v17 deploy. Specific changes:
· Federation Points System reframed as "Ways to Support the Federation" — specific point values and token-allocation promises removed. Three organic actions remain (buy, join Telegram, post on X) with no implied rewards.
· Staking section: added a top-of-section "DESIGN DIRECTION · NOT YET SPEC'D" banner. Specific multipliers and the "20% APY base" projection reframed as draft proposals. The calculator output is now explicitly illustrative. A staking spec, modeled on the liquidation-spec pattern, will be published for public comment before any contract is deployed — that becomes a future entry on this page when drafted.
· Founding Member NFT perks rewritten as "Proposed" with cross-references to the forthcoming staking and governance specs. The fourth perk (raffle priority) replaced entirely with "Permanent on-chain record" — the badge itself is the deliverable. The "⚠ Badges close permanently... No second chances" FOMO line removed.
· Tokenomics pie label "10% REWARDS & RESERVE — Staking rewards · raffles · Founding Member incentives" rewritten to "Post-bond community programs — allocation defined by governance before deployment."
· Roadmap Phase 02 item "Stake2Earn — top holders earn SOL from trading fees" replaced with "Staking design spec published for public comment." Phase 03 "Community governed rates" softened to "Parameters shaped by governance post-launch."
· Both client-side chatbots (home and app) rerouted to POST to /api/chat. The embedded prompts containing Stake2Earn mechanics, specific NFT multipliers, and named privacy-layer vendors were deleted — the disciplined v16 server-side prompt is now the single source of truth.
Home page meta description, Open Graph description, Twitter card description, and JSON-LD Organization description all updated to match the research-first voice in llms.txt. Machine-readable structured data added to this page (Dataset schema) and /security (TechArticle schema).
This entry is part of the public record because the revision itself matters: the point of the corrections log is to document material changes to public-facing claims, not only unbacked promises. A revision this large without an entry here would have been its own kind of failure.
The Federation committed to research-first posture — publishing design thinking in public before shipping code. Up to this point, that posture was visible in the liquidation spec v0.2 and in this corrections log, but there was no dedicated venue for analytical writing that looks outward at where DeFi is heading, separate from the specifications themselves.
Resolution: Kept. On 2026-04-22 the Federation Research Log launched on Paragraph with Week 01: Why intent-based DeFi changes everything — an analysis of the imperative/declarative split in DeFi UX, the solver-competition model (CoW Protocol, UniswapX, Anoma), and why the Federation is studying intent-based architecture for Solana. The post explicitly states that the Federation is not announcing an intent-based product, only documenting that it is studying the direction. Same discipline as Section 7 of the liquidation spec.
Publication terms stated in the post and committed here:
· Weekly cadence. One post per week. Missed weeks will be acknowledged on this page.
· No paywalls. Every post remains free to read.
· No price predictions. The Research Log will not issue targets, forecasts, or trading calls for $GFOF or any other asset.
· No roadmap announcements. New product commitments will continue to happen through the corrections log and versioned specs, not through the Research Log.
· Analytical, not promotional. Posts will analyze the DeFi and Solana landscape. If a post references $GFOF, it will do so in the context of research the Federation is conducting, not as a sales pitch.
The record of the launch: Week 01 on Paragraph ↗. This entry exists because launching a weekly publication with no paywalls or price predictions is itself a public commitment — future entries here will record each Monday's publication (or acknowledge its absence), and the first time any of the five terms above is broken, that break gets its own correction.
The Federation Research Log launched on 2026-04-22 with a binding commitment to a weekly publication cadence. Week 01 published that day. Week 02 was due 2026-04-29 — the first scheduled cadence test.
Resolution: Kept. On 2026-04-29 the Federation Research Log published Week 02: The indexer gap — what pre-bond projects can't see and what to do about it. The essay covers the structural reasons projects below a certain scale are invisible to standard indexing tools (Dune decoded tables, Bubblemaps, DefiLlama) and argues that the surfaces a project controls become the canonical source of trust during this period. It explicitly frames the discipline of pre-bond transparency as the foundation post-bond credibility builds on.
The publication terms committed in #H005 remain in force: weekly cadence, no paywalls, no price predictions, no roadmap announcements, analytical not promotional. Week 02 honors all five.
The record: Week 02 on Paragraph ↗. Week 03 is due 2026-05-06. If it ships, the next entry on this page will record it. If it doesn't, the next entry will record the miss.
The Federation has operated under an implicit posting rule on @GFOF_Offcial: 2–4 measured originated posts per week, reserved for announcements, milestones, Research Log issues, corrections updates, and treasury notes. The rule was correct in spirit but ambiguous about engagement activity — replies, retweets-with-comment, and participation in the broader DeFi conversation.
Resolution: The cadence rule is clarified, not loosened. The 2–4 originated posts per week discipline stands unchanged. Alongside it, three additional bounded practices are now binding commitments on this page:
Off-limits, restated explicitly: Volume bots, paid KOL (paused under #007), hype framing, urgency framing around bond, simulated activity, daily originated posts, raid coordination. None of these are introduced by this revision. The discipline that distinguishes the Federation from category norms is preserved.
Reasoning recorded: The original rule could be read as restricting engagement entirely, or as silent on it. Both readings are unhelpful. This revision clarifies that engagement with the broader DeFi conversation is on-brand at a bounded scale, and creates the tracking infrastructure (#008, #009, #010) to make the new commitments measurable rather than aspirational.
Earlier today, commitment #008 was published with the text "Research Log cross-posted to Medium and Mirror within 24 hours of Paragraph publication." That commitment, as written, is not executable. Mirror.xyz announced its consolidation into Paragraph in September 2025 and the migration completed in late 2025. Mirror no longer exists as a separate publishing surface; visits to mirror.xyz now redirect to Paragraph.
Resolution: Commitment #008 is hereby revised. The cross-post commitment now reads: "Research Log cross-posted to Medium within 24 hours of Paragraph publication." Paragraph remains the canonical surface. Medium remains the secondary surface. Mirror is removed because it is no longer a distinct surface. The original text of #008 is preserved in this entry as the historical record of what was committed before the correction.
Why this entry exists: The Federation's maintenance rules require that "if we find a past statement on the site, in a tweet, or in an article that turned out to be wrong, a correction entry appears here within 48 hours of us noticing." The factual error in #008 was identified before the first scheduled execution of the commitment (Week 03 cross-post, due 2026-05-06), so this correction is filed pre-execution. The first test of #008 will run against the corrected text rather than the original.
Reasoning recorded: Mirror was a credible Web3-native publishing platform when prior cadence-rule drafts referenced it. The platform's consolidation into Paragraph was public information at the time #008 was written and should have been caught before publication. Filing the correction transparently — rather than silently editing the entry or quietly substituting another platform — preserves the discipline that the corrections log itself is designed to enforce. A corrections log that cannot correct itself in public has no integrity.
What this entry does not do: It does not add a replacement platform. The cross-post commitment goes from three platforms (Paragraph + Medium + Mirror) to two (Paragraph + Medium). It does not modify cadence rule #H007's underlying principle. It does not affect commitments #009 or #010.
The Federation Research Log committed to a weekly cadence under #H005 on launch (2026-04-22). Week 01 (2026-04-22) and Week 02 (2026-04-29) shipped on time. Week 03 (due 2026-05-06) and Week 04 (due 2026-05-13) did not ship. Two scheduled posts were missed.
What happened: Federation development bandwidth during the May 5–14 window was concentrated on shipping infrastructure work — SEO foundation, performance pass, FAQ page, research index, custom 404 handling, FCC advance briefing, Dossier integration as the Federation's first Intelligence operation, and the supporting corrections entries for those changes. The Research Log was deprioritized against shipping work. That was a real tradeoff and the Federation made it, but the discipline says missed posts get logged whether the reason was reasonable or not.
Resolution path: A combined Week 03/04 catch-up post ships in Week 05 (window: 2026-05-13 through 2026-05-20) covering the CLARITY Act draft released May 12 and the Federation's posture under its provisions — a topic that genuinely benefited from the delay because the bill text was not available at the original Week 03 deadline. The combined post is filed on Paragraph and cross-posted to Medium per #008 (as revised by #H008).
Cadence going forward: Weekly cadence resumes. Week 06 due 2026-05-27. Week 07 due 2026-06-03. The cadence rule from #H005 stands unchanged — one post per week, missed weeks acknowledged on this page. If volume is genuinely impossible during a given week due to development pressure, the post may be combined with the following week's post on a single topic, but that pattern is the exception not the rule and gets logged here when used.
Status transition: This entry will move from DELAYED to KEPT once the Week 03/04 combined catch-up post is published. Status will be updated in place with the publication date appended. If Week 05 itself slips beyond the 2026-05-20 window, this entry transitions to MISSED and a separate correction is filed addressing why the cadence resumption itself failed.
Reasoning recorded: A weekly publication that goes silent for two weeks without acknowledgment is the failure mode the Federation built the corrections log to prevent. The discipline that distinguishes the Federation from category norms is not "we never miss" — it is "every miss appears on the log, dated, without spin." This entry is that discipline being applied to itself. The Federation's credibility is not damaged by missing two posts; it would be damaged by hiding that they were missed.
RESOLUTION — appended 2026-05-19
The combined Week 03/04 catch-up post, "The CLARITY Act and the Federation's Posture," is published. This entry moves DELAYED → KEPT. Week 05 window (2026-05-13 through 2026-05-20) was met; the entry does not transition to MISSED.
Canonical (Paragraph): paragraph.com/@gfofofficial/federation-research-log-week-0304 ↗
Cross-post (Medium): medium.com/@gfofofficial/federation-research-log-week-03-04 ↗
Honest note on #H008 compliance: #H008 specifies the Medium cross-post should point back to the Paragraph canonical. The Medium post does this in two human-readable places: a "Canonical: Paragraph" link directly under the title, and a full "Cross-posting" section near the foot that names #008/#H008 and includes the complete Paragraph URL. However, Medium's machine-readable <link rel="canonical"> meta tag continues to self-reference the Medium URL. This is a known Medium platform limitation: a custom canonical tag set retroactively on an already-published, natively-authored Medium post is not reliably honored. It was attempted and did not take. This is a platform constraint, not a discipline lapse, and it is recorded here rather than hidden. Forward fix: future Research Log cross-posts will set the Medium canonical at first-publish time (when Medium does honor it), not retroactively. If Medium ships a working retroactive canonical control, this post will be corrected and the change appended here — never silently.
Cadence status going forward: Weekly resumes per #H005. Week 06 due 2026-05-27. Week 07 due 2026-06-03.
Plain statement first: this is the third revision of the cross-post commitment. The chain is #008 → #H008 → #H010. A commitment revised three times is a signal, and the Federation states it as one rather than framing it as routine refinement: the cross-post commitment has been unstable, and this revision exists to make it finally match platform reality so it stops being restated as something it cannot be.
What was committed: Under #008/#H008, Research Log posts are cross-posted to Medium within 24 hours of Paragraph publication, "with canonical link back to the Paragraph original." The implicit expectation was a machine-readable <link rel="canonical"> tag on the Medium post pointing to Paragraph.
What was tested: The machine-readable canonical was attempted two ways. First, retroactively on the Week 03/04 post (documented in #H009) — it did not take. The #H009 forward-fix hypothesized that setting the canonical at first publish would work. That hypothesis was then tested on the Week 06 post: canonical set at first publish. It also did not take. Medium's published meta tag self-references the Medium URL in both cases.
Confirmed finding: Medium does not honor a custom canonical tag pointing to an external domain, regardless of whether it is set retroactively or at first-publish. This is now established by two independent tests, not assumed from one. The #H009 forward-fix is therefore marked invalidated — it was a reasonable hypothesis that testing disproved, and saying so is the discipline working, not failing.
Revised commitment (effective now): Paragraph remains the canonical platform and is published first. The Medium cross-post carries human-readable canonical pointers: (1) a "Canonical: Paragraph" reference in the post header, and (2) a "Cross-posting" section near the foot of the post naming #008/#H008 and containing the full clickable Paragraph URL. The machine-readable canonical tag on Medium is acknowledged as not externally settable — a documented Medium platform limitation, recorded here once, and not re-footnoted on every future post. SEO source-of-record protection rests on Paragraph's first-publication precedence plus the human-readable pointers, which is weaker than a machine canonical but is what the platform permits.
Honest note on the current Week 06 Medium post specifically: the bottom "Cross-posting" section is present and contains a working clickable Paragraph link — this is the functioning mitigation. The header "Canonical: Paragraph" line is present but rendered as plain text rather than a link, due to Medium formatting; it is a weak pointer. The primary functioning human-readable mitigation is the cross-posting section, and it works. The Federation states this granular reality rather than claiming both pointers are equally strong.
Status: KEPT — the commitment is now revised to what the platform can actually deliver, the limitation is documented, and the mitigation that exists is described accurately including its weak point. This entry is appended; #008, #H008, and #H009 are unchanged and remain on the page in full.