Jolly Roger Charter

Draft. JRCv1 is a working conformance standard, not a software licence, and nothing here is certified. Launch status.

Curated summary · not a transcript

Founding archive

This is not a verbatim transcript. It's an editorial consolidation of the founding human–ChatGPT discussion, assembled from the modular founding documents. Wording was edited and turns were merged or left out. SHA-256 of the file as received: 9527520c159a8e2f6e45e4cc0a6a6f359d44d9b2bac64b6db0357ad00bbad9c9.

The Pirate Charter: Founding Archive

Captured October 17, 2026 | Working draft 0.1 | Not yet ratified or launched

You can't pirate what belongs to everyone.

If we can explain how to build it, we should explain how to run it. If we can explain how to run it, we should explain what it costs. And if someone can make it better or cheaper, they should be free to try.

Purpose. Preserve the founding ideas, technical architecture, favorite language, quotations, governance and debate model, reference application, launch approach and risks without confusing agreed principles with unresolved proposals.

Suggested use. This is the consolidated record. The repository-ready files in the companion ZIP can evolve independently. The material is a draft; it does not itself create a license, organization, AT Protocol service or legal data right.

1. The Pirate Charter: Manifesto

Source: MANIFESTO.md

Software Is Free. Your Data Is Yours.

Free. Libre. Truly Free.

Draft v0.1 — proposed founding text, open to challenge and revision

We believe software was always meant to be shared.

Every program builds on discoveries that came before it. Every invention owes something to its predecessors. Every creative act is part of a much larger human conversation. Art is wonderfully derivative. Understanding our influences is one of the joys of art, not evidence of failure.

We reject the premise that useful ideas and creative expression should be artificially scarce. Where we have rights to offer, we seek to give our software freely to everyone. Even this manifesto should be freely copied, remixed, challenged and improved, to the extent we have the rights to grant. We do not ask for monopoly control in exchange for contributing something useful.

We acknowledge those who came before us: artists, hackers, public-domain advocates, free software pioneers, open-source maintainers, and independent developers. We are not claiming to have invented software freedom. We are asking how to make its practical promise more complete.

Free as in libre. Free as in beer. Free as in truly free.

Free to use. Free to study. Free to copy. Free to modify. Free to distribute, host and sell. Free to build a competing business. Free to leave.

No permission should be needed to improve software that its creators have deliberately given to everyone. Anyone may offer a better version, including a commercial one. We welcome the possibility that someone else will serve users better than we do.

You can't pirate what belongs to everyone. Our flag represents permission deliberately given, not permission unlawfully taken from another creator.

We embrace agentic creation.

AI changes the economics of creating software. We embrace agents as collaborators in the complete lifecycle: discovery, specification, implementation, tests, security review, documentation, maintenance and operations.

Open source is not enough. We will strive to publish the development process itself: the intent and requirements, prompts and agent configuration, architectural and design choices, change history, reproducible environments, tests, CI/CD definitions, releases, infrastructure, and the knowledge required to continue.

A machine-assisted contribution is welcome because it is useful and verifiable, not because it was automated. Humans and accountable maintainers remain responsible for security, legality, safety and what is released.

We will not publish private data, secret credentials, third-party protected content or security-sensitive details simply to perform transparency. Necessary exceptions should be disclosed by category and reason wherever safe.

Your data is yours. Always.

Our software is designed around AT Protocol and user sovereignty. The individual should control their identity, personal records and the permissions by which applications access them. A service may process, store, back up and index authorized data but must not confuse being its custodian with owning it.

People should be able to access, export and migrate data; delegate and revoke permissions where supported; and choose another application or provider without an unnecessary penalty. Software vendors must not claim proprietary ownership of users' personal content merely because they host it.

Privacy cannot be guaranteed by a slogan or a protocol alone. We must implement permission boundaries, encryption where appropriate, transparent retention, deletion and export policies, and safeguards for records that involve more than one person. We do not sell personal data or train models on private user data without informed, explicit authorization in the services we operate.

We charge for stewardship, not ownership.

Running software has real costs. Infrastructure, compute, bandwidth, signing, distribution, security, backups, human time, support and maintenance must be funded.

We believe those asking users to fund operations should open their books. We will strive to show real billed costs, estimated usage, allocated expenses, human contributions, operating reserves and pricing methodology with explicit provenance and freshness. No one should have to guess what they are paying to sustain.

Our aspiration is sustainable cost recovery and accountable reserves, not extracting rent from preventing others from copying software. Others are free to charge different prices, including at a profit. Our promise governs our conduct, not their freedom.

Anyone may improve the economics.

Human attention is never free.

We refuse to hide the costs of software in other people's time. A developer's review, a maintainer's interrupted evening, a volunteer's contribution and a user's struggle with a confusing interface all consume something real: human attention. Money may not have changed hands, but value was spent.

We will strive to measure that cost in Quartermaster and describe it in publicly reviewable, monetary terms, without pretending that any person has a fixed price. Valuation assumptions, alternative models and disagreements belong in the open. Real paid expenses, donated labor and user time must remain separate and must never be counted twice.

We will not monetize users' attention by surveilling them or designing software to keep them engaged for its own sake. The aim is to give attention back. A cheaper infrastructure bill is not progress if it makes people spend more of their lives fighting the product.

Human attention is a real cost, even when no money changes hands. Free software should respect your time as much as your freedom.

Open infrastructure is source code too. Anyone can submit a proposal or pull request to an open infrastructure manifest: better hosting choices, less waste, efficient database queries, safer releases, fewer resources or a new cost model.

We should evaluate such proposals in public with estimates, compatibility tests, security and reliability review, approval gates, and measurements after deployment. Savings should benefit the community in transparent ways: lower costs, better reliability, additional features or adequate reserves. Lower price alone is not success if it compromises security, accessibility or resilience.

If we can explain how to build it, we should explain how to run it. If we can explain how to run it, we should explain what it costs. And if someone can make it better or cheaper, they should be free to try.

We invite disagreement.

A charter that cannot survive criticism cannot credibly call itself free. Ask what is missing. Show us where the architecture fails. Show us how a principle would harm someone. Fork the document. Translate it. Offer a better definition of freedom. Publish the objections alongside the answers.

The standard should not require loyalty to a founder, an organization, a vendor, a paid certifier or a symbol. The independent truth of a project's demonstrated freedoms matters more than whose flag it flies.

Software should outlive its creators.

If the author disappears, someone should still be able to build it. If the host closes, someone else should be able to operate it. If a billing provider or AI vendor changes, the project should have a path to move. If the maintainers become untrustworthy, the community should be able to continue. If users wish to leave, they should be able to take their data.

Our success is not how dependent people become on us. It is how useful, accessible, reliable and independent the software becomes.

The code is everyone's. The data is yours. The responsibility is ours, for as long as you choose us.

Free. Libre. Truly Free. Raise the flag.

Legal drafting note: “The code is everyone's” is a normative statement; actual rights are determined by valid project licenses, contributors' ownership, dependencies, patent rights and jurisdiction. “The data is yours” means enforceable control and rights of the appropriate person or participants, not a universal factual assertion that one user owns all data they touch. This is a manifesto, not an operative software license or privacy contract.

2. Charter Principles and Boundaries

Source: CHARTER.md

Purpose

Define an adoptable standard for independently maintainable, user-sovereign software, rather than creating another software copyright license. The manifesto describes values; this charter provides a bridge to independently assessable practice.

Six pillars

Pillar Normative aspiration Evidence to request
1. Creation freedom Permissionless reuse and resale of eligible project code Actual license and provenance, source, dependency inventory
2. Development freedom Complete, portable, agent-neutral project knowledge Specs, decisions, sanitized agent traces, tests, build instructions
3. Data freedom Users control their records and can leave AT Protocol identity/data model, export/migration demo, rights policy
4. Stewardship freedom Other providers can operate and maintain the application Reproducible deployment, incident handbook, release/key transfer plan
5. Economic freedom Honest, auditable operating costs and pricing Public cost report, formulas, caveats, reconciliation and provenance
6. Governance freedom Independent contributors can improve and continue the work Open proposals, documented decisions, multiple stewards, fork rights

Overarching test: The Freedom to Continue

Proposed JRCv1 extension: Economic freedom should include an openly discussed and versioned method for measuring human attention, beyond provider invoices. Distinguish paid labor, imputed volunteer/stewardship attention and user time burden. Avoid compulsory universal person-specific valuations and invasive tracking. See Human Attention Accounting.

A project should be able to demonstrate at least one independent person or organization reproducing its stack, understanding its costs, operating it, upgrading it and performing a complete user-data migration without privileged help from the original creator.

What this is and is not

Compatibility without capture

AT Protocol is a foundational default. Where not appropriate or not yet capable (especially private and organizational records), an application must transparently document a portable and user-controllable alternative or its current limitation; conformance levels should make the distinction visible. Avoid pretending all types of data are supported by AT Protocol today.

“100% agentic development” describes intentional embrace and full process disclosure, not an obligation to remove human accountability or hide human intellectual contribution. Publication must never expose secrets.

Non-negotiable process safeguards

  1. Public issues and transparent rationales for standards decisions.
  2. Human-reviewed changes, threat modeling, CI security checks, and progressive releases for operational changes.
  3. Fair attention to community participants, including right to disengage or fork.
  4. Standards and badge claims must be verifiable; never pay-to-play for permission to use code or voluntarily assess a project.
  5. Project-level financial stewardship commitments must be separable from the copyright license itself.
  6. Adoption must never require endorsing one person's ideology, reputation or personal brand.

3. Decisions and Open Questions

Source: DECISIONS-AND-QUESTIONS.md

Captured October 17, 2026. Confirmed means the user explicitly favored the concept in conversation; it does not imply publication or legal implementation.

Explicitly favored or firmly expressed

Candidate recommendations, not yet final

Open decisions requiring debate

  1. Naming and clearance: Jolly Roger, Pirate Charter, Truly Free, Quartermaster and neutral standard name; trademark/domain search.
  2. Licensing: CC0 for original eligible work? How to address patents and non-waivable rights? What alternatives can an adopter use and still conform?
  3. Brand governance: public-domain graphics vs controlled compliance mark; guard against fake compliance without centralizing control.
  4. Atproto data model: proposed Lexicon names and schema governance; shared/private organizational records; Spaces readiness.
  5. Cost methodology: what counts as stewardship cost, opportunity cost, salaries, volunteer labor, reserves, reimbursements and taxes; transparency granularity.
  6. Economic pledge: how to determine a reasonable reserve and who approves use of excess revenue.
  7. Disclosure policy: precisely which agent logs, credentials, security findings, datasets, employee/customer details cannot be published.
  8. Conformance: how to prevent unverifiable badges or standards capture; target role of independent reviewers.
  9. Governance: initial maintainer selection, voting mechanism, amendment rules, conflict resolution and emergency succession.
  10. Reference app scope: which two cost providers first; which programming languages to prioritize; self-hosted billing credential storage model.
  11. Distribution: order of outreach and launch timing; first independent reviewers and maintainers.
  12. Novelty framing: describe a new synthesis rather than claiming global priority.

Don't lose these exact lines

The code is everyone's. The data is yours. The responsibility is ours, for as long as you choose us.

You can't pirate what belongs to everyone.

Free to use. Free to reproduce. Free to improve. Free to compete. Free to leave.

Our books are open. Our infrastructure is open. Our future is open to contribution.

Could your software survive without you?

The first software movement that hopes you'll copy everything.

The freedom to continue.

4. Conformance: Prove Your Freedom

Source: standard/CONFORMANCE.md

This is a draft assessment framework, not a certification or claim any product already qualifies. The project must publish clear, independent evidence; self-attestation alone is not verification.

Evaluation categories

1. Code and rights

Source available; copyright and dependency provenance documented; redistribution, modification, commercial distribution and forks legally permitted for covered original code. Separate any proprietary or restricted components and document their effect.

2. Development and AI transparency

Durable specifications, design decisions, agent/tool versions and sanitized session context; deterministic tests and published release/build instructions; ability to swap AI agents without losing intent.

3. User data sovereignty

AT Protocol identity and portable data where applicable, documented data boundaries, real export and import, revocable grants where supported, deletion and retention disclosures, special rules for shared/private data.

4. Operations and resiliency

No secret proprietary deployment process; infrastructure descriptions, backup/restore and rollback procedures, reproducible release and self-hosting or independent-provider path. The ability to continue without one maintainer is demonstrated, not merely claimed.

5. Economic transparency

Privacy-safe provider costs, reconciled bills and fresh estimates, manual costs and reserves labeled, methodology, measurement window, per-user/unit costs with denominators and allocation assumptions; public suggestions for cost efficiency.

6. Open community and governance

Accessible issues and proposals; documented review rules, maintainer succession, dispute and appeal process, contribution credits, copy/fork freedoms and an opportunity for independent stewardship.

Progress levels, not a purity contest

Projects should be able to publish evidence for each category independently. Proposed flags:

Never call a self-reported badge an independent certification. Use dated, versioned standards. A project may report '4 of 6 pillars evidenced' and invite help with the remaining two.

Machine-readable report concept

Use an open JSON/YAML manifest with standard_version, project_id, pillar, claim, evidence_uri, evidence_hash, reviewer, reviewed_at, verified and limitations. A public AT Protocol record can point to the report, but the repository must remain usable without a specific PDS or directory operator.

Acceptance test

Ask an outsider to fork, configure a clean environment, build/release, deploy, export a test user's records, migrate them to another provider, calculate operating cost, submit a safe infrastructure-cost PR and test a maintainer handoff. Log blocked steps and use them to improve the standard.

Risks

A standard that is impossible for smaller projects to adopt will not spread. A standard too easy to claim becomes marketing theater. Incremental transparent progress and public evidence should bridge the two.

5. AT Protocol and User Sovereignty

Source: standard/DATA-SOVEREIGNTY.md

Intent

AT Protocol is a core technical pillar because the product should not make the service operator the sole authority over a user's digital identity and records. The goal is meaningful user control and portability, not the legally inaccurate statement that all data is owned exclusively by one person.

Proposed architecture

AT Protocol limits as of October 17, 2026

Promise to users

The service itself will not claim ownership of personal content because it hosts it. It will specify legitimate processing rights and obligations in binding terms. Do not sell personally identifying data or train models on private user information without explicit informed consent in services that adopt the stewardship pledge.

Unanswered design questions

How should collaborative ownership work? How does recovery work when a user loses keys? Can public records be selectively forgotten? How should shared data be exported when participants disagree? What must an app do if atproto support is partial?

Sources: https://atproto.com/guides/overview ; https://atproto.com/specs/lexicon ; https://atproto.com/blog/atproto-spaces-alpha ; https://atproto.com/blog/devex-goals-for-spaces

6. Open Agentic Development

Source: standard/AGENTIC-REPRODUCIBILITY.md

Foundational claim

An application is not truly independently reproducible if others can only copy today's code but lack the intent, context, specifications, release process and operational knowledge necessary to maintain it. Publish the full process, as far as rights, privacy and security permit.

Expected repository artifacts

  1. Product rationale, user requirements, tradeoffs, roadmap and structured specifications.
  2. Architecture decisions and rejected alternatives, including performance and security tradeoffs.
  3. Agent instructions (for example AGENTS.md), model/tool and runtime versions, skills and safe environment setup.
  4. Sanitized prompts, conversation transcripts or equivalent structured intent histories, with provenance and redaction indicators.
  5. Build scripts, lockfiles, dependency manifests, test suites, validation commands and expected outputs.
  6. CI/CD workflows, environment templates, release checklist, release signing method, rollback instructions and deployment playbooks.
  7. Infrastructure-as-code and open infrastructure manifest, with safe stand-ins for secrets and billing IDs.
  8. Security model, responsible disclosure, dependency update process, incident-response playbook and support runbooks.
  9. A contributor path to use any competent coding agent, not one locked proprietary assistant.
  10. Public issue/PR records that connect suggested improvements to tests, accepted decisions and production results.

What FULLY means in practice

Publish enough detail that someone can reconstruct the decisions and produce a functioning independent instance. Not publishing actual credentials, user private messages, undisclosed vulnerabilities, third-party proprietary data, or copyrighted source you cannot redistribute. Use a public redaction policy identifying protected categories and disclose where omissions exist without revealing the protected material.

Agent workflow

Propose -> clarify -> specify -> threat-model -> implement -> test -> compare -> review -> merge -> release -> measure -> publish lessons. Agents can automate bounded work, produce proposed patches and raise safety concerns. Humans authorize critical deployments and operational changes.

Measurements

Existing precedent

GitHub Spec Kit demonstrates specification-driven workflows, agent integration and reproducible development assets. The proposed innovation is to tie this to public-domain intent, independent operations, data sovereignty and cost transparency as a shared movement: https://github.github.com/spec-kit/

7. Open Economics and Infrastructure

Source: standard/OPEN-ECONOMICS.md

Core statement

Our books are open. Our infrastructure is open. Our future is open to contribution.

Provider billing integration, usage-derived projections, manually quantified obligations, reserves and pricing methods should form part of an application’s documented public operating model. Use read-only, least-privilege connectors and publish aggregates safe for public inspection, not the raw credentials or identifiable billing records.

Cost categories

Compute, databases, storage, bandwidth, backups, monitoring, domain and certificates, app-store and release operations, CI/CD, LLM inference and coding agents, customer support, paid human development, professional fees, taxes, insurance, contingency, amortized capital expenses, unpaid volunteer labor when disclosed as donated rather than falsely claimed as cash expense, and operating reserve.

Data quality and display

Distinguish (1) actual finalized invoice, (2) current usage estimate, (3) manual actual, (4) allocated/shared cost, (5) forecast and (6) reserve. Display provider, reporting interval, last sync, currency, exchange assumptions, metric numerator and denominator, rounding and reconciliation status. Public cost-per-user figures should distinguish active users from paying users and specify whether costs are variable or shared.

Reference data architecture

Provider connectors -> ingestion/normalization -> FOCUS-aligned financial events -> private raw store -> aggregation and redaction -> signed public cost snapshot -> dashboards, export and AT Protocol publishing. Maintain provenance and reconciliation links. Cost data is not always available real-time; freshness should be explicit.

Useful existing tools: FOCUS 1.4 for billing normalization; OpenCost for cloud-native cost allocation; Infracost for PR-level infrastructure estimates; OpenTofu for declarative deployable infra. Avoid claiming these tools cover every provider or manual cost out of the box.

Open infrastructure pull requests

The project publishes open-infrastructure.yaml and referenced deployable infrastructure code. A contributor, including an agent, proposes a change: cost savings, performance optimization, alternative provider, smaller instance, caching, storage tier, backup policy or safer release pipeline.

Every PR should include:

A saving that breaks backups, weakens security or increases downtime is not a valid win.

Sustainable pricing

Human attention is part of the economic picture. The proposed Human Attention Accounting extension adds explicit, nonoverlapping views of paid maintenance, imputed donated labor, and user attention burden. The public dashboard should show each separately rather than burying attention under “free volunteer work” or implying that users' lost time appears on an invoice. Pricing cannot simply equal cash bills plus every imputed impact; those are different ledgers.

Transparency is not the same as zero payment. The steward may charge a reasonable amount to cover labor, resilience and ongoing obligations; publish the allocation and rationale. The pledge favors passing efficiencies to the community through lower prices, better quality, reserves or renewed development. Competing providers may price differently; the license must not restrict them.

Open questions

What privacy-safe minimum aggregation threshold applies? How should contributions reducing bills be credited? Should costs be attested by third parties? How much staffing and surplus is appropriate? How do we avoid customer-identifiable unit economics? What happens when an API cannot disclose certain provider pricing?

Sources: https://focus.finops.org/docs/specification/v1-4/ ; https://opencost.io/ ; https://www.infracost.io/ ; https://opentofu.org/

8. Human Attention Accounting: Open Draft

Source: standard/HUMAN-ATTENTION.md

Proposal for JRCv1 discussion, October 17, 2026. The user has explicitly requested that human attention have a monetized representation in Quartermaster and that the underlying valuation be openly, broadly debated. No universally accepted hourly price or methodology has yet been agreed. This document proposes a public and revisable method, not a declaration of consensus or a claim that a person has a market price.

Core principles

  1. Human attention is a real economic resource even when donated. It cannot be treated as free simply because a human did not issue an invoice. Do not confuse valuing time with treating a human being as a commodity.
  2. Software should minimize involuntary demands on attention. A cost-saving change that increases cognitive load, support burden or time spent by users may be a net loss even if cloud bills fall.
  3. Value assumptions are public and contestable. Publish source, location/year/currency, rate-selection process, reference scenarios, uncertainty ranges and adjustment rules. Anyone can submit reproducible criticism or proposals through public PRs, not only accountants or maintainers.
  4. No mandatory global rate. A common measurement standard may be globally discussable while context-dependent rates vary by geography, purpose, opportunity cost and task. Provide community-maintained reference rates and transparently allow local overrides. Never infer that a person with lower wages has less inherent worth.
  5. User time belongs to users. User-attention costs may be estimated from consensual aggregate research or disclosed task models. No covert attention tracking, behavioral scoring, identity-level surveillance or sale of attention data. Do not optimize a product to maximize engagement time.
  6. Avoid double counting. Paid workers' actual compensation is a cash expense; it must not also be added again as an estimated attention expense. Donated/volunteer effort and attention burdens imposed on users appear as separate imputed economic cost categories.

Two core ledgers, three useful lenses

Ledger Description Included in the cash price automatically?
Cash operating cost Provider bills, paid salaries/contracts, support expenses and other actually paid amounts Potentially, according to a published pricing policy
Stewardship attention imputed cost Verified/estimated value of unpaid review, volunteer maintenance, governance, incident response and management attention No; it is a noncash economic contribution unless actual compensation is paid
User attention burden Time spent learning, waiting, troubleshooting, navigating, recovering from errors, or being interrupted No; an external cost borne by users, reported separately

Optional additional lenses: (a) total economic footprint, combining these without overlap; (b) attention avoided, the estimated time saved relative to a documented baseline; and (c) attention debt, foreseeable recurring attention caused by avoidable design/maintenance deficiencies. These are analytical measures, not universally accepted accounting measures.

Calculation v0 proposal

For a task class j: attention_hours_j = instances_j × active_minutes_per_instance_j / 60.

imputed_attention_usd_j = attention_hours_j × declared_reference_rate_usd_per_hour_j.

stewardship_full_cost = cash_operating_cost + imputed_unpaid_stewardship_attention.

total_economic_footprint = stewardship_full_cost + estimated_user_attention_burden.

Paid human time already included in cash operating cost must not be added again as imputed attention. Interruption / context-recovery overhead may be separately modeled only with a documented, nonoverlapping time estimate. Do not imply that money is actually being transferred when a cost is imputed.

Example (illustrative, hypothetical, not JRC's actual rates)

Dashboard displays $700 cash operating cost; $320 donated attention; $1,020 full stewardship economic cost; $2,500 user attention burden; and $3,520 estimated combined footprint, all distinctly labeled. This does not mean Quartermaster should charge users $3,520 or that the user time is revenue. If the organization pays reviewers, their invoices move from the noncash ledger into the paid ledger rather than being counted twice.

Open reference valuation process

Proposed machine-readable record

attention_cost:
  methodology: jrc-human-attention-draft-0.1
  activity: pull_request_review
  perspective: unpaid_stewardship # or user_burden / paid_work
  quantity: 8
  unit: hour
  rate:
    amount: 40
    currency: USD
    basis: illustrative_reference_only
    geography: unspecified
  imputed_amount: 320
  is_cash_expense: false
  measurement: voluntary_aggregate_report
  confidence: estimated
  disclosure: public_aggregate
  reference_period: monthly

For user attention, report observations only in aggregate, with consent and privacy safeguards. A project can use public task benchmarks and opt-in usability studies instead of telemetry. Publish data quality and uncertainty; suppress low-count statistics.

Conformance and decision gates

A JRC application should disclose whether attention is included, for whom, how estimates were obtained, and what is missing. The first conformance levels can require disclosure and methodology, not mandatory adoption of any one dollar value. A project may not claim financial savings while hiding increased maintenance/support/user attention burdens. A PR should report total cost impact and projected attention burden alongside cash savings, security, privacy, resilience, and accessibility.

Intellectual background and caution

The US Department of Transportation uses context-sensitive monetary valuations of travel-time savings for benefit/cost analysis; this shows that time valuation is an established analytical practice, not that there is a universal number for human attention. USDOT guidance. FOCUS 1.4 standardizes provider billed and effective costs; Quartermaster's human-attention imputation must remain separately labeled rather than masquerading as FOCUS-reported bills. FOCUS cost definitions.

Unresolved questions

Who has authority to publish reference rate versions? Should the charter give equal standing to conflicting valuation scenarios? How should involuntary interruption and cognitive load be measured without invasive tracking? Can usability improvements be verified without imposing additional burdens on participants? How do we avoid extracting unpaid work from volunteers by making it look merely like a public cost number? When should attention-reduction projects be prioritized over cloud-bill savings?

9. Quartermaster Reference Application

Source: product/QUARTERMASTER.md

Working name, unverified. First proposed app under the manifesto and practical proof of open economics.

Product thesis

Anyone should be able to assemble a reliable picture of what operating an application costs, publish safely aggregated expenses, invite other people to make it cheaper and then verify the results. Costs and operational architecture should be observable and portable rather than hidden in private spreadsheets and cloud consoles.

Primary capabilities

Technical architecture, proposed

Provider adapters -> secure private ledger ingestion -> FOCUS-style normalization -> reconciliation + manual-entry interface -> redact/aggregate -> public snapshot/event feed -> dashboard, exports, and agent/PR integrations. A configurable privacy boundary sits between provider data and publication. Human approval gates govern operational changes.

API-first implementation

Define OpenAPI specification once; generate official and community SDKs for TypeScript/JavaScript, Python, PHP, Go, Java, C#, Rust and Swift as feasible. Support CLI and simple self-hosted deployment. Prefer a small interoperability core over multiple huge SDKs maintained independently.

First MVP (suggested)

  1. Two billing integrations selected by developer demand.
  2. Manual expense import and labeled reserves.
  3. Reconciliation model and dashboard that distinguishes forecast vs finalized spend.
  4. Basic authenticated admin vs public viewer permissions and safe redaction.
  5. Example open-infrastructure.yaml and a PR cost-diff workflow.
  6. OpenAPI schema plus two generated clients, followed by more languages.
  7. Full published agent sessions (sanitized), tests, decisions, deployment/runbooks, and challenge instructions.

Important product constraints

Cloud billing APIs are delayed and provider-specific; avoid promising truly real-time finalized invoices. Provider read-only credentials still require secret storage and scoped access. Public unit costs could reveal company/customer information at small scales: use aggregation thresholds and optional suppression. Correct for refunds, credits, one-time migration expenses and cross-currency bills. Public cost estimates do not automatically constitute independently audited financial statements.

Natural first story

“Here is a working application. Here are its agent instructions and open infrastructure. Here is what its operation costs. Here is an independent developer's PR that made it cheaper, and the bill showing the effect.”

Competitive differentiation to validate

Existing cost standards and platforms already normalize or optimize spending. Quartermaster's proposed niche is public cost accountability plus community-changeable infrastructure and fully reproducible stewardship. Validate this through prototype users, not marketing claims.

10. Governance and Open Debate

Source: community/GOVERNANCE-AND-DEBATE.md

Governing principle

If the movement only survives while its originator drives every change, it contradicts the freedom to continue. Community stewardship should be explicit, shareable, accountable and forkable.

Founding open debate

Before soliciting badges or celebratory endorsements, invite participants to break the charter. Create a public issue category: What Would Make This Fail? Capture objections, tradeoffs and respectful dissent as first-class contributions. Credit critique that improves the standard.

Proposed open debate prompts:

  1. Is this substantively new, or open source with pirate branding?
  2. Can a public-domain ideal coexist with contribution attribution, trademark and patent rights?
  3. What does genuine data ownership mean for collaborative, organizational or publicly replicated records?
  4. Where does full process disclosure end to protect secrets, privacy, security and third-party rights?
  5. Can labor, taxes, reserves and risk be honestly represented in cost-based pricing?
  6. Who audits the auditors, conformance badges and costs?
  7. Could a project comply technically while using coercive or abusive hosted-service terms?
  8. Can smaller maintainers participate without onerous documentation overhead?
  9. What should survive a protocol or cloud provider disappearing?
  10. Would a competing fork have the right to continue the movement's symbols and specification?

Proposed governance

A voluntary flag, not a monopoly

An optional movement emblem could be useful for discovery, but the right to use the software or apply the open spec must not depend on approval, fee or membership. If accuracy requires controls around a compliance mark, separate those from open content/code rights and establish fair, accountable governance. Naming/trademark clearance remains outstanding.

Contribution credits

Value documentation, careful critique, a repaired deployment, translated material, security fixes, independent reproduction, cost reductions and human support alongside code. Attribution is culturally important even when no enforceable attribution duty is imposed by public-domain dedication.

Community structure

Start with a public repository, issues, pull requests and an open contributor forum. Consider independent maintainers and rotating working groups for legal, protocol, security, economics and communications. Evaluate fiscal sponsorship only if funds or legal administration become necessary.

11. The Independent Survival Challenge

Source: community/THE-CHALLENGE.md

Could your software survive without you?

A practical, repeatable, independently checkable test of the movement's beliefs. The challenge should be reproducible without the inventor's privileged access, organizational membership or approval.

Challenge objective

A person or team who did not build the application should be able to:

  1. Discover all needed source, rights and build specifications.
  2. Reconstruct the intended development workflow using a choice of AI agent or ordinary tools.
  3. Produce a verified build and run automated tests on a clean machine.
  4. Independently deploy the system to an alternate environment with documented assumptions.
  5. Understand infrastructure spending and publish a safe, reconciled cost estimate.
  6. Export a test user's data and migrate it to another authorized provider or compatible application.
  7. Propose a safe, measurable infrastructure-cost improvement through a PR.
  8. Restore from backups and explain the release, patch and security response process.
  9. Demonstrate that updates and continued operation do not require the original creator.

Evidence

Publish: public repository/commit, test environment and dependency versions, build logs stripped of secrets, signed results if available, migration test records with dummy data, cost calculation method and observed blockers.

The standard should reward truthful partial results. If a participant discovers they cannot reproduce an application, document exactly what is missing, then invite others to fix it.

Participation format

No one pays to participate. Community members may host public demonstrations and local gatherings. Never imply third-party projects are endorsed or audited without their permission.

Public hook

Could your software survive without you?

If it can't, help make it possible.

This is a substantive challenge, not an arbitrary viral stunt. The demonstration itself should advance project independence.

12. Zero-Paid-Media Growth Strategy

Source: strategy/ORGANIC-LAUNCH.md

Growth goal

Zero paid media, not zero effort or infrastructure cost. The aim is broad, voluntary adoption generated by useful work and freely reusable content, not manufactured engagement, spam, mass DMs or purchased attention.

Three jobs

  1. Make people care: memorable message and moral case.
  2. Make people believe: evidence, prior-art honesty, working reference tools and meaningful critique.
  3. Make people participate: contribution paths achievable in minutes and deeper maintainer responsibilities.

Three levels of narrative

Distribution avenues and community norms

Who to ask first

A free software historian, copyright and patent expert, AT Protocol engineer, infrastructure/FinOps maintainer, security reviewer, independent open-source maintainer, agent-workflow expert, and artist interested in remix culture. Ask “What's broken? What did we miss?” not “Will you amplify my project?”

Self-propagating mechanics

Suggested 90-day progression (hypothesis)

Period Milestone Evidence to seek
Days 1–7 Publish foundational archive and an invitation to challenge it Independent substantive objections and corrections
Days 8–14 Community-specific conversation and verified historical narrative Discussion outside the founder's network
Days 15–30 Quartermaster thin slice + full reproducible development record One outsider reproduces it without privileged help
Days 31–60 Starter kit + sample machine-readable conformance report + atproto records Two or three outside projects attempt adoption
Days 61–90 Stewardship handoff and independent challenge Improvements occur without founder direction

These are aspirational test milestones, not predictions.

Measurement hierarchy

Best evidence: independently reproduced apps; external implementations; complete user-data migrations; measurable savings; independent maintainers; PRs completed without founder involvement. Secondary signals: followers, impressions, shares, GitHub stars, downloads and media mentions.

Anti-patterns

Don't exaggerate originality; don't attack all prior open-source work; don't create artificial scarcity around badges; don't fake grassroots engagement; don't spend time chasing every network if the product evidence isn't ready; don't use pirate messaging to imply unauthorized copying of others' software; don't burn volunteers with endless compliance tasks.

13. Messaging and Historical Inspirations

Source: strategy/MESSAGING-AND-HISTORY.md

Quotes explicitly retained by request

Thomas Jefferson, letter to Isaac McPherson, August 13, 1813

“He who receives an idea from me, receives instruction himself without lessening mine”

Verified through Monticello's transcription of Jefferson's letter; the passage reflects the non-rivalrous nature of sharing ideas. Do not attribute to Jefferson a blanket opposition to every modern copyright protection; contextualize the 1813 letter, which principally addresses invention/patent questions. Original letters have different spellings and punctuation from common normalized editions.

Source: https://tjrs.monticello.org/letter/293

Steve Wozniak, 1984 Hackers Conference, as recounted by Steven Levy

“Information should be free but your time should not.”

Steven Levy recounts this response to Stewart Brand at the 1984 Hackers Conference, in a 2014 retrospective. This connects shared information and the economic reality of human labor without confusing them.

Source: https://www.wired.com/story/hackers-at-30-hackers-and-information-wants-to-be-free/

Historical lineage

Do not claim no one has attempted similar work. Precedents include GNU, SQLite, Ghost, free culture, Open Source Maintenance Fee, Spec Kit, atproto portability, and FinOps projects. See research/PRECEDENTS.md.

Favorite copy lines

Three communications formats

Headline: Free. Libre. Truly Free.

Short explanation: We don't just share source. We share how it was built, how to operate it, what it costs and how to keep user data portable. Anyone can reproduce, maintain, improve or sell the software, including our competitors.

Manifesto hook: Every creative work owes something to those who came before it. If we can reproduce code with agents, we should also be able to reproduce its process, infrastructure, economics and stewardship. Freedom is the ability to continue without permission.

Design direction, not an approved brand

Pirate flag, naval charts, old proclamations, woodcut and printing-press imagery can evoke anti-monopoly history without implying actual lawlessness. Balance radical storytelling with restrained, credible engineering documentation. Naming and graphic rights must be reviewed before public use.

Open content distribution

Publish a copyable one-page charter, 2-minute talk outline, historically sourced quote cards, presentation slides, accessible alternative text, localized translations, and permission for honest derivative presentations. Quote external authors accurately and respect any independent rights in modern source texts/photos.

14. Prior Art and Originality

Source: research/PRECEDENTS.md

Conclusion: There are clear precedents for each major building block. The combination of public-domain aspiration, complete agentic reproducibility, atproto-centered data control, replaceable stewardship, public operating costs and community-driven optimization is a potentially distinctive synthesis, not a verified global first. A web search cannot prove no earlier implementation exists.

Relevant precedents

Precedent Shared idea Distinction to test
GNU Manifesto / FSF Four freedoms, sharing, paid service can coexist with free code Common GNU strategies use copyleft instead of unrestricted public-domain dedication
SQLite Public-domain software alongside paid support Not a generalized agentic process and public-cost transparency standard
Ghost Open-source, managed hosting, public-facing economics Not generally a public-domain/atproto/agent-log reproducibility program
Creative Commons / CC0 Waiving copyright constraints for owned works Provides legal tools, not service or deployment governance
Free culture / Copyheart / remix movements Art built through copying and transformation Primarily cultural expression and licensing advocacy
AT Protocol Portable identity and data records / open Lexicons Not a blanket privacy or universal operational-cost solution
GitHub Spec Kit Agentic spec-driven workflow, prompts, project process Not the same economic and user-sovereignty pledge
FOCUS / OpenCost / Infracost / OpenTofu Normalized billing, allocation, cost proposals and reproducible infra Proposed charter makes transparency and outside optimization required dimensions of a movement
Open Source Maintenance Fee Explicit maintenance economics Varies in commercial restrictions; this charter welcomes competitors' resale and profit
Early hacker movement and 1984 Hackers Conference Sharing information alongside charging for time Present concept is also about data and independently reproducing operations

Originality claims to avoid

Safer formulation

“We are assembling a practical, independently verifiable standard that brings free software, reproducible agentic development, user-controlled data, transparent operations and competitive stewardship under one charter.”

Research program before large launch

  1. Invite GNU/FSF, OSI, Creative Commons, CC0 and SQLite specialists to identify missing history.
  2. Search academic, legal, maintainer and agentic engineering examples for prior efforts at operational freedom.
  3. Document disputed claims and linked sources in the issue tracker.
  4. Publish corrections promptly and cite intellectual predecessors.

Useful sources: https://www.gnu.org/gnu/manifesto.html ; https://www.sqlite.org/copyright.html ; https://ghost.org/ ; https://creativecommons.org/public-domain/ ; https://github.github.com/spec-kit/ ; https://focus.finops.org/ ; https://atproto.com/guides/overview

Source: legal/LICENSE-AND-RISK.md

This is general planning, not legal advice or a final licensed release.

What is being proposed

The founder's philosophical preference is to place rights-controlled original works as fully into the public domain as legally possible. CC0 is a candidate because it aims to waive copyright and related rights to the extent local law permits, with a fallback license. A proper review must consider non-waivable author/moral rights, jurisdiction, patents, source provenance, imported dependencies and permission from all rights holders.

The standard should not confuse a public-domain dedication with a guarantee that the original creator continues to own all code or that no downstream derivative can acquire separate rights. Copyright in original eligible material and rights to subsequent original modifications are distinct questions.

Important separation of documents

Layer Purpose
Software license / CC0 dedication Legally grants rights over owned eligible source and docs
Manifesto Moral and cultural philosophy; no contract by itself
Open stewardship pledge Provider's voluntary pricing/transparency commitment
Service terms and privacy notice Binding data control and processing obligations of operator
Conformance standard Technical/economic/governance requirements for honest public claims
Trademark/compliance-mark policy Avoid confusing impersonation; separate from code freedom
Contribution policy Provenance, third-party rights, patent review, AI-generated material

Data cannot simply be declared “owned” by a license

Personal records can contain multiple people's information, public data, contractual rights, business records and legally mandated retention. The service's objective is to avoid taking ownership/control unnecessarily, preserve user permissions and provide technically real portability and accountability. Public AT Protocol records are replicable; don't offer a false universal deletion guarantee.

Real constraints

Launch gate before license is finalized

Get input from open-source and patent counsel; clarify ownership of all contributed work; choose licenses for code, docs, media and specs; verify dependencies; clarify volunteer contributor terms; then publish actual legally operative files. Do not assert OSI approval for a chosen tool without checking.

Sources: https://creativecommons.org/public-domain/ ; https://creativecommons.org/faq/ ; https://opensource.org/osd ; https://www.copyright.gov/ai/

16. Contributor and Agent Instructions

Source: AGENTS.md

This repository is a founding document collection, not a deployed product or mature standard. Honor the goals of independent reproducibility and clear human decision-making.

Before making changes

  1. Read README.md, MANIFESTO.md, CHARTER.md and DECISIONS-AND-QUESTIONS.md.
  2. Distinguish confirmed founding preferences, draft implementation proposals, verified external facts and speculative naming.
  3. Prefer substantive revisions with context, evidence, compatibility assessment and documented tradeoffs.
  4. Do not claim legal adoption, technical certification, live integrations, external endorsement or community consensus that doesn't exist.
  5. Never add credentials, personal or payment information, secret vulnerabilities or unlicensed text from a third party to public artifacts.

For an agent creating an implementation plan

Produce: goals; non-goals; acceptance criteria; rights and data boundaries; architecture; open standards; threat model; infrastructure costs and provenance; deployment/rollback; end-user export/migration; reproducibility test; community review proposal; unresolved decisions.

For a proposed standards change

Use an RFC or PR documenting: motivation, principle changed, alternatives, privacy/security/legal implications, migration and conformance effects, public criticism, review result and versioning recommendation.

For a cost-optimization PR

Attach comparable before/after unit costs, one-time expenses, estimate method, performance/security benchmarks, operational risk and an after-deployment measurement plan. No agent may approve its own production changes.

Overarching test

Could someone without this founding team reproduce the code, process, deployment, costs, data migration and maintenance decision without private help? If no, identify the missing dependency and invite a repair.

17. Verified Research Sources

Source: SOURCES.md

This is a list of research references, not a claim of organizational affiliation or endorsement. Statements may change over time.

Historical quotations

Foundational software freedom

User-controlled and permissioned records

Reproducibility and economics

Precedent business models

Further diligence to perform