ANUKA Manifesto

Draft 0.1 — 2 August 2026
This manifesto states the values of ANUKA. The Network State Declaration defines the broader mission, commitments, and boundaries.

We are building a network where quality can move

Talent exists everywhere, but trusted opportunity does not.

People are commonly evaluated through credentials, titles, interviews, and access to institutions. Companies are commonly evaluated through marketing claims, closed dashboards, and snapshots that are difficult to verify. Useful ideas are collected, but the people who produce them rarely share in the value they create.

ANUKA exists to make another model practical:

a person can begin with a bounded real contribution;
a company can expose a safe, specific opportunity;
a result can be tested against an agreed metric;
evidence can be reviewed, corrected, and verified;
reputation can follow the contributor;
value can be shared with the people who created it;
successful products can attract stewards, users, capital, and further improvement.

The objective is not to turn every interaction into a transaction. The objective is to make meaningful contribution visible, portable, and economically useful.

What we value

We are learning how to build better companies, products, and communities by improving real systems and helping others improve them. Through this work, we value:

Verified contribution over claimed credentials

Credentials can be useful context. A record of completed work, reviewed evidence, and measured outcomes is more useful evidence of capability.

Measurable improvement over visible activity

Hours, messages, meetings, and task counts are not the same as value. We prefer evidence that a contribution improved an agreed condition without creating unacceptable harm elsewhere.

Bounded experiments over uncontrolled access

A contributor should be able to influence a real system without receiving unnecessary power over it. Scope, permissions, audience, duration, budget, metrics, and rollback conditions should be explicit.

Learning loops over fixed status

A reputation should evolve through new evidence. A failed, well-designed experiment can be valuable when it produces reliable learning. A past success must not become permanent immunity from review.

Portable reputation over captive profiles

Evidence created in one product should be reusable elsewhere when the participant has the right to share it. The network should not require a person to abandon their history when leaving a platform.

Contextual evidence over universal scoring

No single number can responsibly summarize a person or company. ANUKA should expose relevant evidence, confidence, source, recency, scope, and dispute status instead of manufacturing an opaque universal score.

Human agency over autonomous opacity

AI should reduce friction, expand access, and help people reason. It should not silently assign human worth, hide responsibility, or exercise open-ended authority without a responsible human or organization.

Open protocols over platform captivity

Shared identity, contribution, attestation, and quality primitives should be inspectable and composable. Hosted products may be commercial, but the network must avoid making trust dependent on one irreplaceable vendor.

Product autonomy over central monoculture

Resident products can have different brands, founders, teams, business models, and operating cultures. They should interoperate through the shared core without becoming identical departments of one monolith.

Stewardship over positional hierarchy

Authority should be attached to a declared scope, purpose, duration, risk boundary, and accountability mechanism. A title alone should not justify indefinite control.

Consentful transparency over forced exposure

Transparency is valuable only when it does not become surveillance. Founders and participants should control which non-public evidence is disclosed, to whom, for what purpose, and for how long, subject to applicable law and contractual obligations.

Reversible decisions over irreversible hype

Experiments should have stop conditions. Credentials and attestations should support expiration, revocation, supersession, and correction where appropriate. The network should preserve history without pretending that every historical claim remains current.

Sustainable value over speculative tokenization

A token is not a prerequisite for community, reputation, governance, or payment. ANUKA is tokenless by default and introduces regulated or tokenized instruments only when there is a real use case, legal review, and a safer design than conventional alternatives.

Evidence-based claims over promotional certainty

Claims about quality, growth, readiness, or performance should be supported before publication. ANUKA must distinguish observations, estimates, simulations, opinions, and verified results.

Useful simplicity over feature accumulation

The network should reuse mature standards, SDKs, APIs, and open-source components before building new infrastructure. New primitives are justified only when the missing capability is strategic, generalizable, and not already solved well.

The items on both sides can have value. When they conflict, ANUKA deliberately gives greater weight to the values on the left.

The promise to participants

ANUKA should make it possible to:

discover a real opportunity without first winning a conventional hiring process;
understand the expected result, risk, reward, and review method before starting;
work with the minimum access necessary;
receive attribution for accepted contributions;
contest inaccurate records and add context;
carry permitted evidence to future opportunities;
grow from small, low-risk work toward greater responsibility;
leave without losing the right to evidence they are entitled to retain.

This promise does not guarantee work, payment, acceptance, or positive results. It commits the network to legible rules, fair process, and evidence that can be inspected.

The promise to resident companies and products

ANUKA should help a resident organization:

expose opportunities without exposing its entire internal system;
discover contributors through demonstrated capability;
receive feedback, sponsored demand, testing, and implementation support;
define how a result will be measured before work begins;
preserve control over production changes and confidential information;
build a verifiable history of learning and improvement;
publish selected evidence without fabricating certainty;
access shared identity, reputation, payment, and quality infrastructure without surrendering product autonomy.

The promise to builders

The shared core should be:

open-source where openness strengthens the standard;
API-first and agent-accessible;
documented as code;
versioned and testable;
privacy-aware and secure by default;
modular enough to replace components;
legally usable in commercial products;
understandable without dependence on private institutional knowledge.

What we refuse to become

ANUKA must not become:

a universal social-credit system;
a marketplace that hides employment relationships behind labels;
a pay-to-win reputation directory;
a public leaderboard of private human behavior;
an automated management system with no appeal or accountable operator;
a token project searching for a purpose;
a certification mark based only on self-reported claims;
a centralized product empire pretending to be a decentralized network;
a growth engine that rewards revenue while ignoring safety, privacy, accessibility, or long-term damage.

Progress is a verified learning cycle

ANUKA treats progress as a repeated cycle:

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

Not every signal becomes a task. Not every task becomes an experiment. Not every experiment succeeds. Not every successful metric should be optimized indefinitely.

The cycle is valuable when it creates reliable learning, respects the people affected, and leaves the system more capable of making its next decision.

A living manifesto

This document is deliberately short enough to remember and strong enough to reject incompatible decisions.

Changes should be proposed publicly, explain which value conflict they address, cite relevant evidence, and preserve a versioned history. Fundamental changes should not be hidden inside implementation pull requests.

Sources and influences

Manifesto for Agile Software Development and its twelve principles — value-pair format, continuous delivery, motivated individuals, technical excellence, simplicity, and self-organizing teams.
The Scrum Guide — empiricism, inspection, adaptation, and accountable scopes of work.
NIST AI Risk Management Framework — voluntary, rights-preserving management of AI trustworthiness and risk.
The Open Source Definition — the baseline meaning of open-source software.
W3C Verifiable Credentials Data Model v2.0 — issuer, holder, verifier, privacy, and machine-verifiable credentials.
Ethereum Attestation Service: Attestations — structured, signed claims and the importance of attester reputation.
FTC Policy Statement Regarding Advertising Substantiation — objective claims require a reasonable basis before dissemination.

See the Source Registry for status, scope, and verification dates.

Verification record

External links checked: 2 August 2026
Document status: Draft 0.1
Legal review: Required before ratification or use in binding participant terms