ARGOVITA·Argo Vitae · The Ship of Life

Document I·The Working Governance Draft

The Founder’s Charter.

A proposed accountability model for what ArgoVita may become. It is not a description of a currently operating firm.

Draft 0.2 · corrected 9 July 2026 · not yet effective

Current-status notice: ArgoVita is a pre-incorporation project with one founder. It has no employees, retained specialists, operational staff units, production developer interface, marketplace operations, safety function called The Watch, verifier stack, or permanent public decision log. The architecture below is a working design only.

Article I

Status and Purpose

This Charter records the constraints the founder intends to test before ArgoVita becomes an operating marketplace. Its purpose is to prevent a future use of software or AI from obscuring human accountability. It is not a contract, terms of service, participant consent, study protocol, legal opinion, corporate instrument, or claim that the described systems have been built.

The near-term work is simpler: correct the public record, interview potential posters and participants, obtain qualified counsel, test demand for an observational pilot, and decline to collect sensitive health data until a reviewed framework exists.

Article II

Current Authority

Brandon Baney is the only current operator and decision-maker. AI tools may assist with research, drafting, analysis, and code, but they hold no independent authority to speak for ArgoVita, bind a counterparty, move money, collect participant data, approve a protocol, provide advice, or publish a material claim.

Actions reserved to the founder

  • Any public claim about product capability, incorporation, demand, customers, partners, funding, revenue, safety, outcomes, or regulatory posture.
  • Any decision to recruit a participant, accept a poster, collect health-related information, define a protocol, or launch a pilot.
  • Any contract, investment communication, capital decision, vendor engagement, insurance decision, payment, refund, or use of the ArgoVita name by another party.
  • Any response to a safety, privacy, legal, regulatory, press, or participant complaint.
  • Any amendment to this working draft.

Assistance is not authority. A draft, automation, or agent action is not approved merely because it exists.

Article III

Proposed Future Functions

Earlier materials called these six areas “pods” and described them as operating units. They are not. The list below preserves the design idea while recording the actual status: six possible future functions, each blocked behind evidence, qualified humans, and explicit authority.

Marketplace Operations

Possible purpose

A possible future function for coordinating qualified posters, participants, evidence requirements, and payment workflows.

Status

Not staffed, retained, automated, or operational.

Launch gate

No matching, data collection, payment, or participant communication until counsel, consent, privacy, vendors, insurance, and a funded pilot are ready.

Safety and Participant Support

Possible purpose

A possible future human-led function for screening proposed work, handling participant questions, and routing incidents.

Status

Not staffed, retained, automated, or operational.

Launch gate

No automated safety judgment, medical advice, adverse-event response, or claim that a proposed Voyage is safe for a specific person.

Growth

Possible purpose

A possible future function for evidence-based content, search, partnerships, and measured acquisition.

Status

Not staffed, retained, automated, or operational.

Launch gate

No invented performance, partner, customer, funding, demand, safety, or outcome claim. No unsupervised public outreach.

Content

Possible purpose

A possible future function for drafting the Captain’s Log, public records, and research education.

Status

Not staffed, retained, automated, or operational.

Launch gate

No publication without founder review, source checks, privacy review, and reconciliation with the Claims Registry.

Business Development and Agent Discovery

Possible purpose

A possible future function for interviewing poster and agent-workflow candidates and, only after evidence, designing integrations.

Status

Not staffed, retained, automated, or operational.

Launch gate

No partner label, production API, contract, autonomous counterparty, or commercial commitment without evidence and founder signature.

Support

Possible purpose

A possible future function for policy-bound poster and participant communications.

Status

Not staffed, retained, automated, or operational.

Launch gate

No medical advice, unsupported promise, or automated resolution of a safety, legal, privacy, payment, or consent issue.

Article IV

Gates Before Any Pilot or Automation

A public concept may move toward a pilot only when the evidence and safeguards for that specific pilot exist. At minimum:

  • A real poster problem, accountable budget owner, minimum useful evidence, timeframe, and signed nonbinding pilot- interest letter.
  • Qualified counsel has reviewed the intended activity, jurisdictions, consent and privacy model, research and ethics questions, payment flow, entity posture, insurance, and vendor roles.
  • Participant-facing materials state what is collected, why, who receives it, how long it is kept, how withdrawal works, what compensation means, and where support is available.
  • Vendors, data flows, access controls, retention, deletion, incident handling, payment mechanics, taxes, and failure states have been tested.
  • The pilot is observational unless a later, separately reviewed decision authorises something else. The word “observational” is not treated as a legal exemption.
  • Public copy and investor materials match the evidence and the current Claims Registry.

Automation gate

No software agent may independently approve research, contact participants, make safety judgments, move funds, release data, publish claims, or execute contracts. Any later delegation must be narrow, revocable, logged, tested, and supervised by an accountable human with the relevant competence and authority.

Article V

Records, Evidence, and Amendment

ArgoVita currently relies on ordinary version control and dated project records. It does not have an immutable, append-only operating ledger. A stronger decision record remains a future governance goal, not a current audit surface.

  • Material public corrections should be dated and preserved in history.
  • Claims about demand, money, partners, customers, product capability, and safety require attributable evidence.
  • Investor drafts that contain unsupported claims remain frozen in a clearly marked do-not-send archive.
  • A future effective Charter must be reviewed against the actual entity, contracts, product, team, and legal advice in place at that time.

This working draft may be revised only by the founder. A revision changes the proposed governance design; it does not by itself activate a team, system, role, or authority.

Accountability before autonomy. Set out.

Working-draft owner: Brandon Baney, Founder
For: ArgoVita, a pre-incorporation project
Corrected: 9 July 2026

The Argo Navis, split into three

CARINA

The keel

PUPPIS

The stern

VELA

The sail