Floating Moat Standard

The Floating Moat Standard (FMS) is a proposed framework for classifying competitive defensibility by the point at which a moat's expiration clock begins.

This repository contains version 2.0 of the standard in both Markdown and LaTeX source form, plus a rendered PDF.

Public Console

The repository includes a static frontend in docs/ for GitHub Pages.

The console presents the FMS tier explorer, current Fundscore snapshot, diligence packet navigation, and local Fundscore commands.

Live site: https://sunrisesillneversee.github.io/FMS-2.0-Package/

Ecosystem

FMS is the standard. Fundscore is the companion instrument.

FMS defines how to reason about defensibility. Fundscore checks whether a repository exposes enough public evidence for that claim to be evaluated with discipline.

See ECOSYSTEM.md for the relationship between FMS, Fundscore, and the broader repo-native diligence loop.

Files

• FMS-2.0.md - canonical Markdown source
• FMS-2.0.tex - LaTeX source for PDF rendering
• FMS-2.0.pdf - rendered PDF artifact
• ECOSYSTEM.md - relationship between FMS and Fundscore
• FMS-EVIDENCE.md - checklist for evaluating FMS-style repo evidence
• ARCHITECTURE.md - repository architecture and Fundscore CI flow
• ROADMAP.md - near-term and long-term development path
• RISKS.md - known risks and limitations
• MARKET.md - audience, use context, and adjacent categories
• GOVERNANCE.md - project governance and change principles
• SECURITY.md - security reporting and CI/tooling scope
• docs/ - GitHub Pages static frontend
• Makefile - convenience commands for rebuilding the PDF

Build

To rebuild the PDF from LaTeX:

make pdf

This requires a LaTeX distribution with latexmk and the packages used by FMS-2.0.tex.

To remove LaTeX build artifacts:

make clean

Fundscore

This repository includes fundscore, a deterministic repo-readiness scorer, under fundscore/.

Fundscore does not prove that a project has a moat. It measures whether the repo exposes enough evidence for credible evaluation: roadmap, risks, governance, license posture, tests or CI, security posture, market context, public proof links, and related artifacts.

Run it locally:

cd fundscore
npm install
node bin/fundscore.js .. --md

GitHub Actions runs Fundscore on pushes to main and on pull requests. Pull requests receive a Markdown report comment, and pushes upload the JSON report as an artifact.

Fundscore currently lives in the broader Mos2es_Signomy project and is vendored here for repo-local scoring.

Report Visibility

Fundscore still runs on every push to main, but push report artifacts are optional.

To upload the JSON report artifact on every push, set the repository variable:

FUNDSCORE_UPLOAD_ON_PUSH=true

Manual workflow runs also include an upload_report option. Pull requests continue to receive the Markdown report comment.

Status

• Status: Proposed Standard
• Category: Strategic Defensibility / Systems Governance
• Version: 2.0
• Date: March 2, 2026
• Author: Deric J. McHenry, Ello Cello LLC

Contact

For questions, corrections, or review, contact burnmydays@proton.me or open a GitHub issue or pull request.

License

This work is licensed under the Creative Commons Attribution 4.0 International License.

See LICENSE for the license summary and the full legal code at https://creativecommons.org/licenses/by/4.0/legalcode.