README: reflect both IANA registrations (.faf + .fafm)#10
Merged
Conversation
Updates the README to acknowledge the FAF family's TWO IANA-registered
media types instead of just one. Previously the README treated IANA
registration as singular (referencing only .faf / vnd.faf+yaml). With
`application/vnd.fafm+yaml` registered 2026-05-13 (RT #1451393), the
README now reflects:
- TWO IANA badges side-by-side (vnd.faf + vnd.fafm, FAF cyan #00D4D4)
- TWO Zenodo DOI badges side-by-side (the .faf Context paper + the
.fafm Memory paper, both via the existing centered citation block)
- Updated hero: "IANA-Registered Formats" (plural)
- Updated Historic Milestone heading: "Two IANA Registrations"
- Includes both registration dates (Oct 31 2025 + May 13 2026)
- Cites the verbatim IANA canonical line:
"Two formats. Two lifecycles. One ecosystem."
- Updated IANA Media Types table: TWO rows (one per format)
- Updated Status section: both registrations listed
- Updated Major Milestones chronology: adds May 13 2026 entry
Designed to scale to a 3rd registration via additional side-by-side
badges + table rows when applicable.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per UX feedback: naked DOI numbers (10.5281/zenodo.18251362, .20348942) don't tell readers which paper is which. Switching to shields.io custom badges with semantic labels: [DOI | Context paper] [DOI | Memory paper] FAF orange #FF6B35 per `faf-visual-canon-palette-fonts` doctrine (papers = orange; IANA = cyan; consistent with the FAF visual canon). Tight side-by-side to match the IANA badge pattern. Scales to a 3rd paper later by adding `[DOI | Agent paper]` in the same row. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 22, 2026
Polish pass — consolidate FAF cohort badges to one canonical location instead of splitting IANA (top row) from DOI (centered block). Master template, top of README: [Chrome] [Website] [Spec] [IANA: vnd.faf+yaml][IANA: vnd.fafm+yaml] [DOI: Context paper][DOI: Memory paper] [License] - IANA pair: tight side-by-side, FAF cyan #00D4D4 - DOI pair: tight side-by-side, FAF orange #FF6B35 (Option-1 label-only) - Scales to a 3rd badge per cluster when FAFa publishes This locks the reusable pattern for propagation across the FAF cohort repos (faf-cli, claude-faf-mcp, grok-faf-voice, claude-fafm-sdk) — they will paste this exact markdown via follow-up PRs once #10 is merged. Build once, deploy consistently. The centered DOI block (added in #9) is now redundant and removed — all cohort signals live in one place. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Per design lock — the FAF cohort badge row should lead with credibility receipts, not infrastructure noise: 1-2. [IANA: vnd.faf+yaml][IANA: vnd.fafm+yaml] cyan 3-4. [DOI: Context paper][DOI: Memory paper] orange 5. [Spec v1.1.0] 6. [License: MIT] 7. [Website faf.one] 8. [Chrome Extension] Trimmed: - GitHub stars badge (social style — not needed on the spec repo) - NPM Downloads badge (referenced claude-faf-mcp; belongs there, not here) - Discord badge (no Discord exists) Flow: credibility (IANA + DOI) → standards (Spec) → legal (License) → identity (Website) → distribution (Chrome). This locks the master template for cohort propagation. Same pattern will paste verbatim to faf-cli, claude-faf-mcp, grok-faf-voice, and claude-fafm-sdk in follow-up PRs after this merges. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 23, 2026
Wolfe-Jam
added a commit
to Wolfe-Jam/grok-faf-voice
that referenced
this pull request
May 23, 2026
Sweep + plant per the master template locked on Wolfe-Jam/faf#10: - Removed old Zenodo-style DOI badge - Prepended cohort prefix at credibility-first position: [IANA: vnd.fafm+yaml] [DOI: Memory paper] [existing: PyPI · Python · License · Tests] .fafm-only class: 1 IANA badge (cyan) + 1 DOI badge (orange Option-1). Same canonical pattern across all FAF cohort repos. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wolfe-Jam
added a commit
to Wolfe-Jam/claude-faf-mcp
that referenced
this pull request
May 23, 2026
Applies the master template locked on Wolfe-Jam/faf#10: - Cohort 2+2 badges at top of README (IANA pair + DOI pair, both-formats class): [IANA: vnd.faf+yaml][IANA: vnd.fafm+yaml] [DOI: Context paper][DOI: Memory paper] - New CITATION.cff (CFF 1.2.0) — preferred-citation = Context paper, references += Memory paper. - New ## Citation section with both papers + BibTeX. Per feedback-update-via-repos-canonical-channel doctrine — same canonical pattern across all FAF cohort repos. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wolfe-Jam
added a commit
to Wolfe-Jam/faf-cli
that referenced
this pull request
May 23, 2026
#68) Applies the master template locked on Wolfe-Jam/faf#10: - Cohort 2+2 badges at top of README (IANA pair + DOI pair, both-formats class): [IANA: vnd.faf+yaml][IANA: vnd.fafm+yaml] [DOI: Context paper][DOI: Memory paper] - New CITATION.cff (CFF 1.2.0) — preferred-citation = Context paper, references += Memory paper. - New ## Citation section with both papers + BibTeX. - IANA-singular drift fix: Line 1 stamp now says 'CLI for the .faf and .fafm IANA-registered formats' Line 278 lists both vnd.faf+yaml (Context) and vnd.fafm+yaml (Memory) Per feedback-update-via-repos-canonical-channel — same canonical pattern across all FAF cohort repos. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wolfe-Jam
added a commit
to Wolfe-Jam/faf-mcp
that referenced
this pull request
May 23, 2026
#39) * README: cohort template (IANA + DOI badges + Home + Live demo) + CITATION.cff Brings faf-mcp into line with the FAF Foundation cohort badge treatment locked on Wolfe-Jam/faf#10 and propagated to faf, faf-cli, claude-faf-mcp, grok-faf-voice, claude-fafm-sdk on 2026-05-23. Class: .faf-only (single IANA cyan + single Context-paper DOI orange); npm description is "IANA-registered .faf format", so claim is true. Changes: - Add cohort badges row immediately after hero (IANA cyan + DOI orange) - Add Home line (faf.one — no dedicated path exists yet; root is honest fallback per the Home doctrine in feedback-update-via-repos-canonical- channel) - Add Live demo line (faf-mcp.vercel.app, verified 200) per SDK/builder- class dual-link pattern - Sweep redundant badges: NPM Downloads (noise), Website (replaced by Home line), Deploy-Vercel inline button (replaced by Live demo line) - Keep: CI, npm version, License, project.faf-inside - Add CITATION.cff (CFF 1.2.0; preferred-citation = Context paper DOI 10.5281/zenodo.18251362) — powers GitHub Cite-this-repository sidebar Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * README: Home → faf-mcp.vercel.app (per wolfejam directive) For faf-mcp specifically, the Vercel app IS the canonical face — no dedicated faf.one path exists yet for the IDE Edition MCP, and faf.one/mcp is owned by claude-faf-mcp. This is an explicit exception to the locked Home = always CF doctrine in feedback-update-via-repos-canonical-channel — for repos that have no CF page yet, the Vercel app substitutes as canonical Home. Live demo line dropped (would duplicate the Home URL). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wolfe-Jam
added a commit
to Wolfe-Jam/grok-faf-mcp
that referenced
this pull request
May 23, 2026
…TION.cff (#51) Brings grok-faf-mcp into line with the FAF Foundation cohort badge treatment locked on Wolfe-Jam/faf#10 and propagated to faf, faf-cli, claude-faf-mcp, grok-faf-voice, claude-fafm-sdk on 2026-05-23. Class: .faf-only (single IANA cyan + single Context-paper DOI orange); npm description is "IANA-registered .faf format", so claim is true. The repo references .fafm only as a companion-repo pointer (to grok-faf-voice), not as a format the MCP itself serves. Changes: - Add cohort badges row inside centered hero (IANA cyan + DOI orange) - Add Home line (faf.one/grok, verified 200 — vendor-label path is the live canonical for the Grok-specific MCP) - Add Live demo line (grok-faf-mcp.vercel.app, verified 200) per SDK/ builder-class dual-link pattern - Sweep redundant badges: NPM Downloads (noise), inline "Deploy with Vercel" button (huge visual weight, replaced by Live demo line), standalone Vercel-Live badge (replaced by Live demo line) - Keep: mcpaas, CI, npm version, License, project.faf-inside, Chat-to- FAFA - Add CITATION.cff (CFF 1.2.0; preferred-citation = Context paper DOI 10.5281/zenodo.18251362) — powers GitHub Cite-this-repository sidebar Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Wolfe-Jam
added a commit
to Wolfe-Jam/faf-cli
that referenced
this pull request
May 23, 2026
PR #68 (master template propagation) and #70 (Home line) both merged on 2026-05-23 — but the diffs landed INSIDE the Quick Start fenced bash block at line 182, where they rendered as plain gray text, not as badges. The cohort signal was effectively invisible on the rendered README, and the Quick Start bash example was visually corrupted. This PR completes what #68 + #70 intended: - Lift the cohort row (IANA cyan + DOI orange) + Home line OUT of the Quick Start code block, into the canonical top position immediately below the hero div — matching the locked master template on Wolfe-Jam/faf#10 + the 6 other cohort repos. - Restore the Quick Start ```bash block to its original clean state (just bunx commands, no buried markdown). - Sweep redundant badges from the top cluster per the master pattern: NPM Downloads (noise), Website (replaced by Home line), Built with Bun (info-only fluff). - Keep: FAF/mcpaas, TAF, CI, npm version, Homebrew, License, project.faf-inside. Verify-the-deliverable lesson — the merge SHAs landed but the rendered surface didn't. Catching this only via the cross-cohort render check. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The README treated IANA registration as singular (only
.faf/vnd.faf+yaml). Withapplication/vnd.fafm+yamlregistered 2026-05-13 (RT #1451393), the README now acknowledges TWO IANA-registered media types in the FAF family.Changes
Badges
vnd.faf+vnd.fafm), each linking to its own IANA record. Switched from generic blue to FAF cyan#00D4D4(per FAF visual canon)..fafContext paper DOI badge alongside the existing.fafmMemory paper DOI badge in the centered citation block. Both DOIs side-by-side.Header / hero
Historic Milestone section
.faf) + May 13 2026 (.fafm)IANA Media Types table
.faf|.fafm), one column per formatStatus section + Major Milestones chronology
vnd.fafm+yaml)Visual / brand consistency
#00D4D4per[[faf-visual-canon-palette-fonts]](was generic blue)Forward-compatible
Designed so a third registration can be added by:
Test plan
🤖 Generated with Claude Code