Skip to content
ANUKA Foundation

ANUKA Network State Declaration

Draft 0.1 — 2 August 2026
This is a living founding document. It describes ANUKA’s direction, commitments, and boundaries. It is not a claim of sovereignty, a financial offering, or a substitute for legal agreements.

In one sentence

Section titled “In one sentence”

ANUKA is an open network state where people, companies, products, and AI agents improve real businesses through verified contributions—and earn portable reputation and economic opportunity from measurable results.

Why ANUKA exists

Section titled “Why ANUKA exists”

The internet made information globally accessible. Open source made software globally composable. Digital payments made commerce programmable. Yet productive opportunity is still constrained by credentials, hiring funnels, organizational borders, and trust that is difficult to verify.

A person may be capable of improving a product but have no practical way to demonstrate it without first being hired. A company may need help but be unable to assess who can be trusted. A useful contribution may disappear inside a private project history instead of becoming portable evidence of talent.

ANUKA exists to make a different path possible:

  1. enter through a real opportunity;
  2. make a bounded contribution;
  3. test it safely;
  4. measure the result;
  5. verify the evidence;
  6. earn compensation and reputation;
  7. gain access to more consequential work.

The network is organized around quality as a shared economic value: the capacity to make a person, product, company, or system demonstrably better.

What we mean by a network state

Section titled “What we mean by a network state”

The original network-state thesis describes a highly aligned online community capable of collective action that may eventually develop physical presence and formal recognition. ANUKA adopts the useful starting point—an online community aligned around a moral innovation and capable of coordinated action—without claiming present sovereignty or diplomatic status.

For ANUKA, Network State is a design horizon:

  • a digital-first community with a shared mission;
  • a portable identity and contribution layer;
  • an economy that rewards verified value creation;
  • a portfolio of independently operated resident products and companies;
  • transparent, versioned rules;
  • the capacity to coordinate online and, where useful, in person;
  • voluntary entry, participation, and exit.

ANUKA is not a nation-state, government, court, bank, employer of every participant, securities exchange, or universal judge of human worth.

The moral innovation: quality can become a network

Section titled “The moral innovation: quality can become a network”

ANUKA is founded on a simple proposition:

Quality should not remain an internal department. It can become an open, measurable, and rewardable network activity.

Participants can discover problems, propose changes, fund features, run experiments, test releases, improve operations, explain results, and verify outcomes. Companies can expose only the opportunities and evidence they choose, while retaining control over sensitive systems and data.

The network does not reward activity merely because it occurred. It aims to reward contribution according to evidence, context, risk, and observable value.

The network has two layers

Section titled “The network has two layers”

1. The shared core

Section titled “1. The shared core”

The ANUKA core is common infrastructure that products and communities can reuse:

  • identity and authentication;
  • participant and company passports;
  • contribution records;
  • reputation evidence;
  • attestation schemas;
  • permissions and bounded access;
  • opportunities, bounties, and applications;
  • payments and reward routing;
  • quality protocols;
  • dispute and correction records;
  • shared APIs, SDKs, CLI tools, and AI skills;
  • governance and proposal interfaces.

The core should be open, composable, inspectable, and replaceable at the component level. The network should prefer mature standards and open-source infrastructure over rebuilding solved problems.

2. Resident products and companies

Section titled “2. Resident products and companies”

ANUKA may contain many products, services, communities, and companies operating under different brands. Each resident product should be able to:

  • solve one problem exceptionally well;
  • maintain its own roadmap, economics, and customer relationships;
  • operate through an appropriate legal entity or contractual structure;
  • become independently profitable;
  • publish selected opportunities into the ANUKA network;
  • consume shared identity, reputation, verification, payment, and governance services;
  • leave or migrate without losing the historical integrity of participant contributions.

ANUKA is therefore not a monolithic super-app. It is a shared operating and trust layer beneath a growing ecosystem of focused products.

Who can participate

Section titled “Who can participate”

Participation may include:

  • contributors who complete work or experiments;
  • testers and qualifiers who evaluate whether a result is ready and useful;
  • customers and community members who provide feedback, vote, or fund demand;
  • founders who bring products and companies into the network;
  • product stewards who temporarily operate a bounded part of a product;
  • experts and reviewers who issue domain-specific assessments;
  • investors and capital partners who evaluate permissioned evidence;
  • AI agents acting under identifiable human or organizational authority;
  • resident companies and products that publish work and consume network services.

A participant should be able to begin with a small, low-risk contribution. Access to higher-impact opportunities should emerge from relevant evidence, not social status alone.

Work without the hiring bottleneck

Section titled “Work without the hiring bottleneck”

ANUKA should make it possible to contribute before entering a conventional employment relationship.

A typical opportunity may define:

  • the problem;
  • the permitted actions;
  • required skills or evidence;
  • available systems and data;
  • success and safety metrics;
  • review and acceptance rules;
  • compensation;
  • intellectual-property terms;
  • privacy and security obligations;
  • the legal relationship between the parties.

A participant may accept an opportunity, perform the work using their own methods within the agreed constraints, submit evidence, and receive review. The result may become part of a portable contribution history.

This model does not automatically make every participant an independent contractor. Under U.S. rules, worker classification depends on the actual relationship, including behavioral control, financial control, and the relationship between the parties—not merely the name used in a contract or interface. Every resident company must structure work lawfully in the jurisdictions involved.

Product stewardship

Section titled “Product stewardship”

ANUKA distinguishes stewardship from permanent hierarchy.

A product steward may receive bounded authority for a defined:

  • product or operational area;
  • term;
  • budget;
  • permission set;
  • risk limit;
  • metric set;
  • decision scope.

While acting as steward, a participant is accountable for transparent decisions, evidence, handoff, and the protection of customers and assets. Stewardship may be extended, transferred, or concluded according to documented rules.

Stewardship does not itself confer company ownership, equity, employment, fiduciary office, or unrestricted access. Those rights exist only when a separate valid agreement explicitly grants them.

The long-term goal is to let capable people earn progressively greater responsibility through demonstrated judgment—not through title accumulation alone.

Reputation is evidence, not a social score

Section titled “Reputation is evidence, not a social score”

ANUKA rejects a single opaque score that attempts to rank an entire person or company.

Reputation should be a portable graph of contextual evidence. A contribution record may include:

  • subject and issuer;
  • role performed;
  • scope and permissions;
  • source systems;
  • metric definition;
  • baseline and observation period;
  • experiment or review method;
  • result and uncertainty;
  • reviewers or validators;
  • timestamp and expiration;
  • revocation or correction status;
  • conflicts of interest;
  • disclosure level.

Different observers may evaluate the same evidence differently. ANUKA can provide transparent scoring models for specific use cases, but every material score must be explainable, contestable, versioned, and traceable to underlying records.

Cryptographic verification proves properties such as origin, signature, integrity, status, and timestamp. It does not by itself prove that a claim is true. The credibility of evidence depends on the source, issuer, measurement method, and verifier policy.

The quality protocol

Section titled “The quality protocol”

ANUKA quality claims should follow an evidence chain:

signal → hypothesis → authorized action → observation → review → attestation → reward → learning

A public quality badge or passport must never be purchasable as an unsupported endorsement. Objective claims shown to customers or investors must have a reasonable evidentiary basis before publication.

The protocol should support several levels of assurance:

  1. self-declared — published by the subject;
  2. source-connected — derived from an identified system;
  3. reviewed — examined by a qualified participant or process;
  4. experimentally supported — linked to a documented test;
  5. independently verified — confirmed by a separate trusted party;
  6. cryptographically attested — signed and integrity-protected;
  7. continuously monitored — updated as the underlying state changes.

No level should imply more certainty than its evidence supports.

The economy of verified contribution

Section titled “The economy of verified contribution”

The ANUKA economy may support:

  • fixed-price bounties;
  • milestone payments;
  • funded feature requests;
  • testing and qualification rewards;
  • grants;
  • usage-based compensation;
  • outcome bonuses;
  • revenue sharing where legally and contractually appropriate;
  • community funding mechanisms;
  • fees for infrastructure, verification, discovery, and coordination.

A feature can move from request to funded demand, implementation, testing, release, and measured effect. This transforms feedback from an opinion stream into a market signal and, where appropriate, a delivery budget.

ANUKA is tokenless by default. A native speculative token is not required for identity, reputation, governance, attestations, or payments. Any future tokenized instrument, equity interest, profit right, or investment product must be separately designed and reviewed under applicable law. Marketing must never imply investment returns where no compliant investment arrangement exists.

Open source and public infrastructure

Section titled “Open source and public infrastructure”

The network should publish the components required for interoperability:

  • protocols and specifications;
  • schemas and vocabularies;
  • SDKs and reference implementations;
  • verification methods;
  • contribution and governance templates;
  • security and privacy guidance;
  • migration and export formats.

Software should use appropriate OSI-approved licenses. Public documentation should use an open content license. Commercial products may charge for hosting, managed operations, AI inference, compliance, premium workflows, marketplaces, support, and enterprise services.

Open source is not the absence of a business model. It is the decision to make the foundational rules and interfaces inspectable and reusable so that the ecosystem can outgrow any single application.

AI is an amplifier with accountable authority

Section titled “AI is an amplifier with accountable authority”

AI agents may discover opportunities, analyze systems, propose experiments, generate implementations, test changes, summarize evidence, and coordinate workflows.

Every consequential agent action must have:

  • an identifiable principal;
  • explicit permissions;
  • bounded tools and data access;
  • logs and provenance;
  • evaluation criteria;
  • escalation and rollback paths;
  • human or organizational accountability.

AI-generated output is not trusted merely because it is generated quickly. It must pass the same evidence, security, review, and outcome standards as human work.

The purpose of AI in ANUKA is not to make people economically irrelevant. It is to lower the cost of experimentation and help more people discover, demonstrate, and compound their talents.

Privacy and participant control

Section titled “Privacy and participant control”

The subject of a passport should control what is presented publicly unless disclosure is required by a valid agreement or law.

ANUKA should practice:

  • data minimization;
  • selective disclosure;
  • purpose limitation;
  • explicit consent for sensitive publication;
  • separation of public proofs from private source data;
  • revocation and correction;
  • retention limits;
  • export and portability;
  • protection against correlation and doxxing.

Where possible, sensitive metrics should remain offchain. Public ledgers should contain only the minimum evidence needed for verification, such as schemas, signatures, hashes, timestamps, revocation state, and references to permissioned records.

Governance: honest before decentralized

Section titled “Governance: honest before decentralized”

ANUKA begins as a founder-led network. It should not pretend to be decentralized before participants possess meaningful rights, transparent processes, and functioning alternatives.

Governance should evolve through versioned documents and public proposals. The process should reflect empirical principles found in agile and Scrum: transparency, inspection, adaptation, short feedback cycles, working outcomes, and self-organizing teams.

The founding governance commitments are:

  • rules are published and versioned;
  • material changes include rationale and migration paths;
  • product-level decisions remain with the accountable product where possible;
  • network-level decisions apply only to shared infrastructure and standards;
  • conflicts of interest are disclosed;
  • decisions can be reviewed against evidence;
  • participants can contest records and leave the network;
  • decentralization is earned through operational maturity, not declared by branding.

Rights of participants

Section titled “Rights of participants”

Subject to safety, law, and specific agreements, ANUKA aims to protect the following rights:

  1. the right to begin with an accessible contribution;
  2. the right to understand the rules of an opportunity;
  3. the right to know how work will be evaluated;
  4. the right to receive agreed compensation for accepted work;
  5. the right to portable evidence of contribution;
  6. the right to selective disclosure of personal and company data;
  7. the right to correction, response, and appeal;
  8. the right to inspect material scoring logic;
  9. the right to export data in documented formats;
  10. the right to decline opportunities and exit the network.

Responsibilities of participants

Section titled “Responsibilities of participants”

Participation also carries responsibilities:

  1. represent identity, skills, and evidence honestly;
  2. respect permissions and data boundaries;
  3. disclose relevant conflicts of interest;
  4. avoid manipulation, collusion, Sybil activity, and metric gaming;
  5. protect users from unsafe experiments;
  6. document material decisions and limitations;
  7. respect intellectual property and confidentiality;
  8. follow applicable law and product-specific agreements;
  9. correct known false or misleading claims;
  10. improve the network’s shared quality through responsible feedback.
Section titled “Legal and institutional boundaries”

ANUKA’s vocabulary is architectural and cultural; it does not override law.

  • “Resident” does not create citizenship or immigration status.
  • “Passport” does not replace a government identity document.
  • “Steward” does not automatically create ownership, office, employment, or fiduciary status.
  • “Bounty” does not determine worker classification or tax treatment.
  • “Attestation” does not guarantee the truth of its underlying claim.
  • “Quality verified” must be limited to the evidence and methodology actually verified.
  • “Fund a feature” is a purchase, pre-order, contribution, grant, or other defined transaction—not automatically an investment.
  • “Network State” does not imply sovereignty, diplomatic recognition, policing power, or immunity from regulation.

Operational products must add jurisdiction-specific terms for employment, payments, taxes, intellectual property, consumer protection, privacy, securities, money transmission, sanctions, and dispute resolution.

How to join the founding network

Section titled “How to join the founding network”

At the founding stage, a person or organization can participate by:

  • contributing to the open specifications or software;
  • proposing a resident product;
  • publishing a bounded bounty or test opportunity;
  • completing and documenting a contribution;
  • testing a product or funded feature;
  • designing schemas for contribution and quality evidence;
  • reviewing security, privacy, economics, or legal risks;
  • funding open infrastructure or a clearly defined product outcome;
  • helping ratify and improve this declaration.

The first objective is not to simulate a complete society. It is to prove a repeatable loop in which open opportunity produces verified quality, fair reward, and durable reputation.

Founding commitments

Section titled “Founding commitments”

ANUKA commits to building toward these principles:

  1. Contribution over credentials. Demonstrated work should create opportunity.
  2. Evidence over authority. Important claims should be inspectable.
  3. Quality over activity. Busyness is not the primary measure of value.
  4. Experiments over opinion battles. Safe tests should resolve what evidence can resolve.
  5. People amplified by AI. Automation should expand human agency.
  6. Portable reputation. Participants should not lose their history when changing products.
  7. Founder-controlled disclosure. Companies choose what becomes public, subject to law and agreements.
  8. Open standards over lock-in. Core interfaces should remain composable.
  9. Focused products over a monolith. Each resident product should earn its existence.
  10. Transparent governance over theatrical decentralization. Power should be visible before it is distributed.
  11. Consent and exit. Membership and participation are voluntary.
  12. Continuous evolution. The network improves through short cycles of action, observation, and adaptation.

Status and ratification

Section titled “Status and ratification”

This document is a founding draft, not a final constitution.

A future ratification process should define:

  • who may propose changes;
  • review periods;
  • required evidence and impact analysis;
  • approval thresholds;
  • protected principles;
  • versioning and migration;
  • emergency amendment rules;
  • the relationship between network governance and resident-product autonomy.

Until that process exists, the founder maintains editorial responsibility and publishes material changes through the repository history.

Sources and precedents

Section titled “Sources and precedents”

The following primary or first-party sources informed this declaration. They are references and precedents, not endorsements of ANUKA.

Network-state concept

Section titled “Network-state concept”
  • The Network State in One Sentence — the original project’s informal and extended definitions. ANUKA deliberately uses a narrower present-day meaning and does not claim sovereignty or diplomatic recognition.

Empirical and adaptive organization

Section titled “Empirical and adaptive organization”

Verifiable evidence and attestations

Section titled “Verifiable evidence and attestations”

Community funding and contribution allocation

Section titled “Community funding and contribution allocation”

Open licensing

Section titled “Open licensing”

U.S. operating boundaries

Section titled “U.S. operating boundaries”

Verification record

Section titled “Verification record”
  • Links checked: 2 August 2026
  • Source preference: primary standards bodies, official documentation, official repositories, and U.S. government sources
  • Legal review: required before launching employment, investment, token, marketplace, or cross-border payment functionality
  • Next scheduled factual review: before ratification or within 90 days, whichever occurs first