From 83ef42f1a70ff4b40f235f2e52370360081048d6 Mon Sep 17 00:00:00 2001 From: Satonaka Date: Sun, 23 Aug 2026 16:13:23 -0700 Subject: [PATCH] Clarify public core and sustainable support --- profile/README.md | 156 ++++++++++++++++++++++++++++++---------------- 1 file changed, 103 insertions(+), 53 deletions(-) diff --git a/profile/README.md b/profile/README.md index 51cf36c..7c49b33 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,89 +1,139 @@ # TitleChain Foundation -**Open, implementation-neutral standards for human-rooted identity, accountable technology, and sovereign participation.** +**Open standards and public reference infrastructure for portable, interoperable, and owner-controlled identity, credentials, data, agents, records, and authorized digital assets.** -TitleChain Foundation stewards public specifications and review processes that help people retain authority over their identities, credentials, data, and delegated digital actions. +TitleChain Foundation stewards public specifications and review processes designed to help people and legal entities retain authority over what belongs to them, how it may be used, and which humans, agents, tools, or services may act on their behalf. -Our public standards program is **ICSN — Internet Cooperative for Sovereign Networks**. The work is developed through open RFCs, documented governance, public review, conformance evidence, and independent implementation. +Our public standards program is **ICSN — Internet Cooperative for Sovereign Networks**. ICSN develops implementation-neutral specifications for human-rooted identity, portable credentials, meaningful consent, recovery, provenance, accountable delegation to software and AI agents, and conformance across independent implementations. -## Constitutional stewardship +## Start here -**Built for stewardship, not acquisition.** +- **[Read the current ICSN work](https://github.com/TitleChain-Foundation/icsn-standards)** — specifications, schemas, RFCs, governance, and conformance materials. +- **[Review the public capability-profile template](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/templates/M5ISYOU-ONE-PAGE.md)** — a standalone design that does not require an IAM account, M5 membership, or a connected M5 service. +- **[Review the capability schema](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/schemas/m5isyou-capability-profile.schema.json)** — build compatible tools or propose improvements. +- **[Choose a public task](https://github.com/TitleChain-Foundation/icsn-standards/issues)** — contribute code, schemas, tests, documentation, accessibility, security, or implementation review. +- **[Join Discussions](https://github.com/orgs/TitleChain-Foundation/discussions)** — ask questions, test early ideas, and participate in public review. +- **[Read the contribution guide](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CONTRIBUTING.md)** — understand the RFC and pull-request workflow. -The Foundation's constitutional model is anchored by the **TitleChain Sovereign Purpose Trust**, a Wyoming purpose-trust structure designed under its governing framework for a maximum term of one thousand years. +If open, human-controlled digital infrastructure is relevant to your work, please **star [icsn-standards](https://github.com/TitleChain-Foundation/icsn-standards)** and follow [@TitleChain-Foundation](https://github.com/TitleChain-Foundation). Stars help reviewers, implementers, contributors, and public-interest institutions discover the work; they do not create governance authority or imply endorsement. -The purpose is continuity: preserve a human-first digital framework across generations while keeping constitutional stewardship separate from commercial operation. +## The public core -The public commitments are simple: +### Sovereign identity at no charge to the individual -- human authority remains the root; -- privacy and meaningful consent are structural requirements; -- people retain portability, recovery, and the right to exit; -- no sponsor, vendor, implementation, founder, or funder buys unilateral control through money or adoption; -- coercive surveillance and forced vendor lock-in are inconsistent with the mission; and -- M5 is one implementation environment, not the owner of the standard. +The Foundation's first public-infrastructure commitment is a human-controlled IAM identity origin offered at no charge to the individual and designed to preserve foundational access over time. -**[Read the Trust & Non-Capture summary](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/TRUST-AND-NON-CAPTURE.md)** +The architecture supports progressive and plural evidence pathways rather than assuming every person begins with the same institutional documents. Self-asserted origins, member-approved attestations, portable learning and work evidence, and optional institutional or jurisdictional credentials can participate according to their stated assurance and legal context. -The public summary does not replace the Trust instrument, Foundation governing documents, or applicable law. +An IAM identity origin does not by itself establish citizenship, immigration status, regulated identity verification, eligibility for a financial service, or authority to represent another person or legal entity. -## Start here +- **[Access the no-charge IAM starting point](https://m5bank.app/)** +- **[Read the Public Infrastructure Commitment](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/PUBLIC-INFRASTRUCTURE-COMMITMENT.md)** -- **[Explore ICSN Standards](https://github.com/TitleChain-Foundation/icsn-standards)** — specifications, schemas, RFCs, governance, and conformance work. -- **[Review open issues](https://github.com/TitleChain-Foundation/icsn-standards/issues)** — choose a concrete task or suggest an improvement. -- **[Join Discussions](https://github.com/orgs/TitleChain-Foundation/discussions)** — ask questions and participate in public review. -- **[Read the contribution guide](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CONTRIBUTING.md)** — understand the RFC and contribution workflow. -- **[Review current priorities](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/ROADMAP.md)** — see where help is most useful. -- **[Meet the program and extended ecosystem](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/TEAM-AND-ECOSYSTEM.md)** — activation leadership, product delivery and the extended ecosystem are separated clearly. +GitHub participation never requires IAM, M5 membership, or program enrollment. -## Public infrastructure: identity at no charge to the individual +### A free, standalone capability profile -The first public-infrastructure commitment is a human-controlled IAM identity origin offered at no charge to the individual and designed to preserve that no-charge foundational access over time. +The blank M5-CV / M5isYOU capability template is a public design for a standalone capability record. The Foundation's commitment is to release an expressly open-license version that anyone may use, copy, adapt, or improve without requiring an M5 connection. It helps a person describe what she knows, what she can do, what she has done, what she can teach, and what evidence she chooses to present. -The two entry points are deliberately separate: +Until that open-license designation is published in the standards repository, the current asset-level license matrix controls reuse of the public-review template. -- **Free IAM:** **[m5bank.app](https://m5bank.app/)** — the no-charge foundational identity-origin account. -- **Program enrollment:** **[m5member.netlify.app](https://m5member.netlify.app/)** — the M5Member enrollment/activation pathway through which an eligible participant progresses toward her **M5BankofMe account** and applicable program experience. +Connecting a capability profile to IAM, credentials, M5, or another compatible implementation is optional and requires a separate affirmative choice. Connected services must respect the applicable consent, privacy, portability, correction, export, withdrawal, and revocation boundaries. -Free IAM does not require program enrollment. IAM and M5 participation are both optional for standards participation; neither is required to read, review, contribute to, fork, or independently implement ICSN work. +### M5Core and the Freedom Office reference environment -- **[Read the Public Infrastructure Commitment](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/PUBLIC-INFRASTRUCTURE-COMMITMENT.md)** -- **[100K Women-Led Venture Activation](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/100K-WOMEN-LED-VENTURES.md)** — the first scaled activation goal. -- **[M5AgentClub First-100 Activation](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/M5AGENTCLUB-FIRST-100-ACTIVATION.md)** — the first reference activation environment. -- **[M5Brain Reference Architecture](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/M5BRAIN-REFERENCE-ARCHITECTURE.md)** — the member-controlled knowledge/context layer. +M5 is one optional implementation environment used to test how the public principles work in practice. Its developing core connects: + +```text +no-charge IAM identity origin + ↓ +portable capability profile and evidence + ↓ +member-controlled data, knowledge, and context + ↓ +Freedom Office / M5Shell + ↓ +human-authorized M5Agents + ↓ +documented MCP and OpenAPI integrations + ↓ +learning, business, and operating workflows + ↓ +member-controlled provenance and outcomes +``` + +The goal is a portable working environment in which models, applications, integrations, and service providers can change while the person or legal entity retains control of identity, data, credentials, permissions, records, and authorized assets. -## Current public work +Finance, accounting, ledgers, payments, social systems, registries, education, communications, and other services may connect through documented interfaces. They are optional integration layers, not mandatory dependencies of the public standards or standalone capability profile. -- Human-rooted identity and proof of life, presence, intent, and authority. -- Accountable, limited, and revocable delegation to software and AI agents. -- Portable credentials, data provenance, recovery, and the right to exit. -- Security, privacy, conformance criteria, schemas, and reference implementations. -- Interoperability across organizations, communities, institutions, and jurisdictions. -- Public-interest activation infrastructure that can test whether sovereignty works in practice. +M5 does not own ICSN, and an M5 implementation does not become a standard merely because it is deployed. Reusable lessons must enter the ordinary public RFC, review, security, privacy, and conformance process. -All work in this organization should be treated according to its stated maturity and license. Publication does not by itself make a proposal a stable Foundation standard. +## From the first 100 to 100,000 women-led ventures -## Open standards and implementation +The first scaled activation goal is to support **up to 100,000 women-led ventures** with a sovereign digital starting point and a pathway to learn, build, prove, operate, teach, and earn without surrendering ownership of identity, credentials, business memory, or standards governance. -TitleChain Foundation governs the public standards process. M5 and other implementers may test or deploy the standards, but no implementation, vendor, contributor, or sponsor controls the standards solely through funding or adoption. +The first 100 members are the reference learning and activation environment: -Private operational systems, personal records, credentials, and production secrets do not belong in these public repositories. +```text +I AM → I KNOW → I CAN → I DID → I CAN TEACH → I CAN EARN +``` -## Support the public work +Members may activate their own Freedom Office, learn to operate authorized agents, apply capabilities to real work, create or strengthen a business, and—if qualified—help train and activate additional members and businesses. The goal is a distributed network of operators, professionals, developers, educators, trainers, and entrepreneurs rather than permanent dependence on one centralized platform. -Sponsorship helps fund public specifications, security review, conformance materials, reference implementations, release work, open-source tooling, public infrastructure, and contributor coordination. +- **[Read the 100K Women-Led Venture Activation plan](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/100K-WOMEN-LED-VENTURES.md)** +- **[Review the First-100 reference activation](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/M5AGENTCLUB-FIRST-100-ACTIVATION.md)** +- **[Explore the member-controlled knowledge architecture](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/initiatives/M5BRAIN-REFERENCE-ARCHITECTURE.md)** -Sponsorship does **not** purchase governance authority, conformance status, preferential technical decisions, ownership of the commons, or access to private participant data. +The initiative is a program goal, not a claim that 100,000 participants have already been admitted, funded, trained, or activated. -- [How sponsorship works](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SPONSORS.md) -- [Public impact reporting](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SPONSOR-IMPACT.md) +## Help build and sustain the public core -Higher-level organizational partnerships are available through a conversation so scope, recognition, independence, conflicts, and public impact reporting can be agreed responsibly. **[Connect with the Foundation](mailto:hello@titlechainfoundation.org).** +Open standards, security review, documentation, reference implementations, conformance tooling, public infrastructure, and activation capacity require sustained support. + +- **Sponsor the work** — support specifications, security and privacy review, conformance materials, open tooling, release work, no-charge public infrastructure, and activation capacity. +- **Contribute** — help with code, schemas, validation, test vectors, documentation, accessibility, integrations, threat analysis, and public review. +- **Implement** — build independent compatible tools and publish evidence that portability and interoperability work across implementations. +- **Review** — participate in RFC, governance, privacy, security, recovery, and conformance review. +- **Partner** — organizations interested in public-interest infrastructure, education, security, implementation, or activation support may **[contact the Foundation](mailto:hello@titlechainfoundation.org)**. + +Sponsorship does **not** purchase standards authority, conformance status, preferential technical decisions, ownership of the commons, access to private participant data, or control of owner-held assets. + +- [How sponsorship supports the public work](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SPONSORS.md) +- [Public impact-reporting model](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SPONSOR-IMPACT.md) **Fund the commons. Never own the commons.** -## Community standards +## Current technical status + +- **Standards maturity:** early public draft and public review; publication does not by itself create a stable Foundation standard. +- **Current focus:** human-rooted identity, portable credentials and capability evidence, accountable agents, provenance, consent, recovery, privacy, security, and conformance. +- **Public artifacts:** specifications, RFCs, JSON Schemas, validation tools, implementation examples, governance materials, and activation reference architectures. +- **Participation:** public issues, Discussions, RFC comments, pull requests, security review, and independent implementation. +- **Versioning:** see the [changelog](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CHANGELOG.md), [releases](https://github.com/TitleChain-Foundation/icsn-standards/releases), and [roadmap](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/ROADMAP.md). + +All published material must be used according to its stated maturity and asset-level license. + +## Constitutional stewardship + +**Built for stewardship, not acquisition.** + +The Foundation is structured to preserve long-term, human-first public stewardship while separating constitutional governance from commercial implementation. Its purpose-trust model is designed for continuity, independence, and resistance to capture. + +The public commitments are simple: + +- human authority remains the root; +- privacy and meaningful consent are structural requirements; +- people and legal entities retain portability, recovery, and the right to exit; +- funding, adoption, vendor status, or implementation scale do not create unilateral control; +- coercive surveillance and forced vendor lock-in are inconsistent with the mission; and +- M5 is an implementation environment, not the owner of the standard. + +**[Read the Trust & Non-Capture summary](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/TRUST-AND-NON-CAPTURE.md).** The public summary does not replace the Trust instrument, Foundation governing documents, or applicable law. + +## Public-repository boundaries + +Private operational systems, personal records, credentials, authentication material, wallet information, participant evidence, and production secrets do not belong in these public repositories. -Participation is governed by our [Code of Conduct](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CODE_OF_CONDUCT.md), [Governance policy](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/GOVERNANCE.md), and [Security policy](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SECURITY.md). +Participation is governed by our [Code of Conduct](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CODE_OF_CONDUCT.md), [Governance policy](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/GOVERNANCE.md), [Contribution guide](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/CONTRIBUTING.md), and [Security policy](https://github.com/TitleChain-Foundation/icsn-standards/blob/main/SECURITY.md). -We welcome developers, reviewers, security researchers, documentation contributors, implementers, educators, and public-interest institutions. +We welcome developers, reviewers, security researchers, documentation contributors, implementers, educators, sponsors, and public-interest institutions.