Core concepts

An approach we can test, learn from, and change.

The projects are different, but we return to a few common questions.

Who can create something useful together? Connect people with complementary needs, skills, and resources.

What did they agree to do, and what happened? Keep useful evidence of the work and its outcome.

What should the next interaction learn from this one? Use the record to improve decisions, cooperation, and the rules around them.

These ideas are at different stages of development. The full model described here is a research direction, not a system operating across every WebTree project today.

Circles and the concepts

Impact, Pressure, and Imprint

ConceptPlain explanationImportant boundary
ActorA participant: a person, project, organization, AI agent, service, or workflowUsing one technical model does not make human and machine rights or responsibilities identical
CircleA group with a purpose and its own rulesPeople can belong to several; Circles can contain Circles
Interaction historyA record of commitments, actions, and outcomesA report is not automatically a verified fact; privacy still matters
ImpactPositive value attributed under a Circle’s rulesContext and evidence determine what it means
PressureResource use, costs, burdens, or harm attributed under those rulesLegitimate resource use and wrongdoing must remain distinguishable
ImprintA contextual interpretation of contribution using Impact and PressureIt is not a universal score of a person’s value; no final universal formula is settled
TrustAn estimate of whether a particular commitment will be fulfilled under particular conditionsReliability in one activity does not establish reliability everywhere
SkillThe ability to perform a particular activityA useful contribution or a popular reputation does not establish every relevant skill
ReputationWhat others currently believe about a participantPerception can differ from evidence and calibrated trust
Governance authorityPermission or influence over a specific decisionIt should not follow automatically from a contribution score
Contribution inheritanceKeeping earlier useful work connected to what others build on itAn ancestry link is not proof of a precise financial entitlement
Responsible DemocracyA research idea in which decisions develop a track record that can inform governance credibilityAttribution, minority protection, and decision rights remain unresolved
ForkingCreating an alternative project or rule set from an earlier stateAssets, obligations, private data, and branding do not automatically transfer
Cooperation stabilityWhether the system makes reliable cooperation attractive under realistic incentivesThis is a system question, separate from individual Imprint

History and interpretation are different

Illustrative example — not a reported order.

Imagine a Maker reports a successful print and the customer confirms that it fits. Later use reveals a defect.

The original acceptance still happened. The defect report also happened. A useful history contains both, along with the design version, relevant conditions, and any disagreement about the cause.

A group may improve how it evaluates such evidence. It should still be possible to see what the old rules said, what the current rules say, and why they differ.

That is what we mean by rules that can improve over history that cannot be quietly rewritten.

Keep the context attached

A record of manufacturing work can help assess a manufacturing commitment. It cannot measure a human life, establish someone’s worth, or automatically determine their rights.

We want the system to make evidence understandable, show uncertainty, allow correction and challenge, and give newcomers a fair way to participate.

Explore trust and contribution · Read the governance questions

The terminology has evolved: Imprint was also called Influence in earlier writing. The current term is Imprint. An early Impact-minus-Pressure formula is a simplified hypothesis within a rule set, not a settled universal measure. A Circle is a cooperation and governance boundary; a Project Cell is an execution boundary.