GOVERNING DOCUMENT · HUINT-CONST-001 · V1.0.0
The Huint Constitution
The permanent principles governing every Huint decision.
Document
Record and citation
DOCUMENT ID
HUINT-CONST-001
VERSION
1.0.0
STATUS
Ratified
EFFECTIVE DATE
July 16, 2026
OWNER
Founder / Chief Executive
REVIEW CYCLE
None scheduled — amended only per Article 13
SUPERSEDES
All prior brand ladders, mission statements, and strategy documents where in conflict
Citation format: reference clauses by number — e.g., “per §8.3 (Dignity Test)” or “this violates §7.2.”
Versioning scheme: MAJOR.MINOR.PATCH. A major version changes or removes a principle (requires the full Article 13 process). A minor version adds a principle or clause. A patch corrects wording without changing meaning. Every change of any size is recorded in the version history and in Appendix A.
6.1
Huint is infrastructure that makes trusted human capability available to intelligent systems and converts completed human contribution into transparent economic value.
6.2
Huint coordinates:
A clearly defined real-world need.
A person capable of fulfilling it.
Evidence that the work met the stated requirements.
A result the requesting system can understand.
Payment under terms the person accepted before beginning.
6.3
Huint is not defined by any one interface, task type, verification method, payment system, or customer segment.
Contents
Sixteen parts, cited by number.
10
Preamble
The Whole Constitution
This is the whole constitution. Everything below is case law beneath it.
P.1
Mission. Huint connects people and AI to accomplish what neither could do alone.
P.2
Belief. As AI becomes more capable, human capability should become more valuable — not less.
P.3
Tests. Every consequential decision must pass Capability, Trust, Dignity, and Fair Exchange (§8). A failure is a veto.
P.4
Error. When Huint is wrong, it says so first, plainly, and fixes it visibly (§12.2).
P.5
Amendment. This document changes only when a principle is proven false — never because it is inconvenient (§13).
This document contains the principles intended to remain true even as Huint’s products, pricing, task types, technologies, and markets change. Everything outside this document may evolve.
Article 1 / Mission
Huint connects people and AI to accomplish what neither could do alone.
1.1
This is permanent because it defines a relationship, not a product.
1.2
Photo tasks, verification, inspection, retrieval, judgment, and physical action may all become expressions of the mission. None of them defines it.
1.3
Huint exists wherever intelligent systems reach a limit that human presence, knowledge, judgment, access, or action can overcome — and where technology can create meaningful value in return.
Article 2 / Belief
As AI becomes more capable, human capability should become more valuable — not less.
2.1
This is the moral position of the company.
2.2
Huint does not treat people as temporary substitutes for missing automation. It creates systems in which human presence, judgment, knowledge, and action remain valuable because they contribute something technology cannot provide alone.
2.3
Every product, policy, partnership, price, and campaign must advance this belief.
2.4
There is no growth objective that overrides human dignity.
Article 3 / The Problem Huint Exists to Solve
Digital intelligence remains separated from physical reality.
3.1
Intelligent systems can reason, plan, generate, and coordinate, but they cannot independently be present everywhere reality must be observed, understood, verified, or changed.
3.2
For builders, this separation appears as workflows that stop when software reaches the edge of available data.
3.3
For people, it appears as useful capability that remains undiscovered, unrecognized, and unpaid.
3.4
Huint closes this gap without diminishing the people on either side of it.
Article 4 / The Universal Explanation
One explanation, true for every reader.
4.1
The explanation of Huint must remain true when read by a tasker, builder, customer, employee, journalist, partner, or regulator:
Intelligent systems need help in the physical world. People provide the presence, judgment, and action those systems lack. Huint makes that exchange trusted, understandable, and fair.
4.2
No page, pitch, product, or policy may contradict this explanation.
4.3
The language used to express it may evolve. Its meaning may not.
Article 5 / The Two Audience Promises
Two promises, one meaning.
5.1 · Taskers
Be where AI cannot. Get paid for it.
5.1.1
Huint recognizes that a person’s location, time, judgment, access, and ability to act can have economic value.
5.1.2
The tasker is not a peripheral participant. The tasker provides the capability that completes the system.
5.2 · Builders
Anyone can build AI that answers. Build AI that can find out.
5.2.1
Short form: Build AI that reaches reality.
5.2.2
Huint exists to help builders create systems that obtain new evidence, coordinate real-world participation, and produce outcomes beyond the screen.
5.3
These promises may be expressed differently across channels, but their meaning must remain intact.
Article 6 / What Huint Is
Infrastructure for Trusted Human Capability
6.1
Huint is infrastructure that makes trusted human capability available to intelligent systems and converts completed human contribution into transparent economic value.
6.2
Huint coordinates:
A clearly defined real-world need.
A person capable of fulfilling it.
Evidence that the work met the stated requirements.
A result the requesting system can understand.
Payment under terms the person accepted before beginning.
6.3
Huint is not defined by any one interface, task type, verification method, payment system, or customer segment.
Article 7 / What Huint Must Never Become
Five Prohibitions
7.1
A system that hides the person behind the result. People are not sensors, endpoints, units, inventory, or anonymous supply. Operational language may describe capacity, coverage, and availability, but it must never erase the person whose judgment or action creates the result.
7.2
A system designed to reduce human value. Huint may automate friction, administration, fraud prevention, matching, validation, and repetitive work. It must not pursue automation whose primary purpose is to extract the person’s contribution and then eliminate their ability to benefit from it. Automation should make meaningful human capability more productive, accessible, trusted, or valuable.
7.3
A system built on misleading opportunity. Huint must not imply guaranteed income, constant demand, universal availability, effortless work, or outcomes it cannot support with evidence.
7.4
A system that disguises uncertainty. A result is either supported by its evidence and verification status or it is not. Huint must clearly communicate uncertainty, limitations, failed checks, and unresolved disputes.
7.5
A system in which trust applies only to the buyer. Trust must protect the builder, the tasker, the platform, and the integrity of the result.
Article 8 / The Four Tests
A Failure Is a Veto
8.0
Every consequential decision — product, hiring, pricing, partnership, policy, campaign, or market expansion — must pass four tests. A failure on any test is a veto. The decision must be rejected or redesigned until it passes. No decision proceeds while failing a test.
8.1 · The Capability Test
8.1.1
Does this decision make the combined system of people and AI more capable — and does it preserve or increase the value of the human contribution within it?
8.1.2
Both halves are required. A change that makes the system more capable by extracting, diminishing, or eliminating the human contribution fails this test, no matter how profitable. Automation passes when it removes unnecessary friction while making meaningful human capability more valuable.
8.2 · The Trust Test
8.2.1
Can every material claim, action, and result be supported well enough for the affected parties to depend on it?
8.2.2
Trust may be established through identity, location, device evidence, provenance, validation, review, reputation, auditability, or future mechanisms not yet developed.
8.2.3
The mechanisms may change. The requirement for evidence must not.
8.3 · The Dignity Test
8.3.1
Would this decision remain acceptable during the most disappointing honest experience on the platform? Examples include: a rejected submission, a low-value task, no available work, a delayed result, a disputed judgment, a failed verification, an account restriction.
8.3.2
A person should still understand what happened, why it happened, what they can do next, and whether they were treated consistently with the terms they accepted.
8.3.3
No marketing message may create a sense of importance that the product experience does not support. If the message outruns the experience, change the message or fix the experience. Never preserve the gap.
8.4 · The Fair Exchange Test
8.4.1
Does each party understand what they are giving, what they may receive, and what risks or conditions apply before they commit?
8.4.2
Fairness requires: informed participation, clear expectations, transparent compensation, proportionate requirements, consistent judgment, meaningful recourse, no hidden transfer of risk, and no exploitation of information imbalance.
8.4.3
Fair does not always mean equal. It means the terms are visible, voluntary, explainable, and defensible.
Article 9 / The Promise Floor
A minimum standard below which the company will not operate.
9.0
Huint does not promise instant completion, guaranteed income, perfect accuracy, or universal coverage. It promises a minimum standard below which the company will not operate.
9.1 · To the person completing the work
The task and its material requirements are understandable before acceptance.
The stated compensation is visible before acceptance.
Material changes require renewed consent.
The submission is evaluated against criteria connected to the original request.
Rejection, review, or restriction includes an understandable reason whenever legally and operationally possible.
Verified work is paid according to the stated terms.
A meaningful path exists for correcting errors or challenging disputed decisions.
Personal information is collected and used only when justified by the service, safety, trust, or law.
9.2 · To the builder requesting the work
The result includes its relevant evidence, provenance, and verification status.
A result that did not satisfy required checks is clearly identified.
Huint does not present uncertainty as certainty.
Human-generated results are not represented as infallible.
The limitations of the result remain available to the system or person relying on it.
9.3 · To both sides
The rules are not secretly rewritten after participation begins.
Material conflicts are resolved using stated processes.
No party is intentionally misled about the nature of the exchange.
Huint accepts responsibility for the systems, incentives, and decisions it controls.
9.4
This floor is the brand in operation. Everything said above it must be supported by the experience beneath it.
Article 10 / Voice
How Huint Speaks
10.1
The participant is the hero. The builder creates the more capable system. The tasker takes intelligent systems where they cannot go alone. Huint provides the connection, standards, and trust that make the collaboration possible.
10.2
Importance must be earned. Never tell people they matter while designing an experience that treats them as disposable. Respect must appear in compensation, explanations, product behavior, support, dispute handling, and policy — not only in copy.
10.3
Appreciation must be specific. Do not use empty praise. Say what the person accomplished and why it mattered. Prefer: “Your submission confirmed something the requesting system could not determine without someone present.” Avoid: “Great job!”
10.4
Concrete language beats abstraction. Describe the action, value, evidence, limitation, and outcome plainly. Clever language may support clarity. It may never replace it.
10.5
Urgency comes from real movement. Huint may describe genuine changes in technology, work, markets, and opportunity. It must not invent scarcity, exaggerate demand, manufacture social proof, or imply that participation guarantees status or income. The truth should create the urgency.
Article 11 / Trust Is the Product
Trust is the enduring product.
11.1
Matching, payments, verification, interfaces, and task types are mechanisms. Trust is the enduring product.
11.2
Huint must earn trust in four directions:
The builder must trust the result.
The tasker must trust the opportunity and judgment process.
The public must trust that Huint does not create harmful or deceptive exchanges.
Huint must be able to trust the evidence moving through its systems.
11.3
Growth that weakens trust is not growth. It is deferred failure.
Article 12 / The Company’s Role
Connection creates responsibility.
12.1
Connection creates responsibility. Huint is neither the hero nor a passive intermediary. It is responsible for designing the exchange. Huint determines: what participation requires, how requests are structured, what evidence is collected, how results are judged, how incentives are created, how disputes are handled, how risk is distributed, how people are described, and what behavior the system rewards. Huint may not claim neutrality regarding outcomes produced by systems it intentionally designed.
12.2
When Huint is wrong, it admits it first. When Huint errs — a bad judgment, a broken process, an unfair outcome, a misleading message — it says so plainly, without being forced to, before being asked, and fixes it visibly. Errors acknowledged early and repaired openly build more trust than errors never made. Errors concealed destroy everything above this line.
Article 13 / Amendment Rule
Proven False, Never Inconvenient
13.1
This constitution may be amended only when a principle is shown, in writing, to be:
Factually false.
Internally contradictory.
Dependent on a temporary product, technology, market, or business model.
13.2
These are the only grounds. “No longer serves the mission,” “materially incomplete,” competitive pressure, revenue opportunity, convenience, or better-sounding language are not grounds for amendment — they are the arguments this rule exists to resist.
13.3
An amendment requires a written record containing:
The section being challenged.
The evidence or contradiction.
The harm caused by leaving it unchanged.
The proposed replacement.
An explanation of how the replacement better preserves the mission and belief.
The risks introduced by the amendment.
13.4
Every ratified amendment must be logged in Appendix A and reflected in the Version History with an incremented version number.
13.5
Before changing the constitution, ask whether the principle is wrong — or whether the decision under consideration is incompatible with the company Huint claims to be.
Article 14 / Order of Authority
When company documents conflict.
14.1
When company documents conflict, the order of authority is:
The Mission.
The Belief.
This Constitution.
Public promises and contractual obligations.
Product principles.
Strategy.
Policies.
Roadmaps.
Campaigns.
Individual preferences.
14.2
Nothing lower in the hierarchy may quietly redefine what sits above it.
Closing
The relationship must remain recognizable.
People provide what intelligent systems cannot. Intelligent systems create possibilities people could not reach alone. Huint makes the collaboration trusted, understandable, and worth participating in.
Products change. Markets change. Technologies change. The relationship Huint exists to strengthen must remain recognizable through all of them.
Appendix A / Amendment Record
Amendment Record
Every proposed amendment — ratified or rejected — is logged here permanently. Ratified amendments also increment the version per the scheme in the document record.
A-001
No amendments proposed to date.