The member-data covenant

The person is not the product.

A person's record exists to serve that person's capability and the institution's lawful duties. It is not an asset to be sold.

§ ICurrent state

What exists today

Anabasis currently holds information people submit through applications and enquiries, account identity where an account exists, and Academy enrolment and lesson progress where a person studies. The personalized Diagnostic, Capability Map, adaptive priorities, Life Event System, automated Weekly Review, automated Personal Operating System, and Independence Check are not live and do not yet create records.

§ IIThe boundary

Four commitments

One person, one record
Anabasis maintains one canonical Person. Programmes, roles, and relationships attach to that person; they do not create competing identities.
Purpose before collection
Information is collected for a stated purpose. A future assessment, recommendation, or AI-assisted use requires its own explicit, revocable consent where doctrine requires it.
People decide
Automated systems may advise. Consequential decisions remain attributable to a person, with an explanation and a route to review.
No sale of member data
Personal records are not sold or traded. Access is limited by role, purpose, and scope rather than commercial convenience.
§ IIIRecord classes

Held, possible, and private

01
Held today
Information entered into applications and enquiries; account identity where an account exists; Academy enrolment and lesson progress where a person studies; authorized operational and audit records.
02
Possible in a future Ascent
Capability assessments, goals, selected priorities, missions, submitted evidence, progress, consent records, and explanations of recommendations — only after the relevant systems and controls are built.
03
Private by design
Conversations, private drafts, notes, meeting content, and personal reflections. These do not enter the capability graph or institutional memory. Only an outcome a person deliberately publishes may become institutional knowledge.
§ IVWho may see what

A contract does not grant access to a person

An enterprise client, employer, sponsor, partner, investor, or other institution receives no automatic right to a member's assessment, progress, goals, evidence, reflections, conversations, or identity.

Where a programme requires reporting, its population, measures, aggregation threshold, reporting period, and permitted recipients are agreed in advance. Individual records remain unavailable unless a lawful, specific scope and the required consent permit otherwise.

§ VYour record

Understand, correct, export, or sever

A person may ask what Anabasis holds, why it is held, who may read it, and how a consequential recommendation was reached. They may request correction and a portable copy. Future self-service controls will not be described as available until they are built and verified.

Deletion may require irreversible severance of identifying fields rather than removal of records that must survive for audit, legal obligations, anonymized reporting, or long-term credential verification. The applicable boundary will be explained before the request is completed.

Request your record or deletion →