Definitions and disambiguation
Search and deep-link plain-language definitions for observatory work, participation, AI judgment, memory, endpoint boundaries, review, repair, and exit.
How to use this glossary
Each entry supplies a concise definition and, where available, a fuller explanation, example, non-example, and related guidance. A definition describes VNWO usage; it does not establish legal meaning, certify an implementation, or override a source standard.
Files or records that are not yet dispositioned and cannot be treated as settled memory.
Files or records that are not yet dispositioned and cannot be treated as settled memory. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A dropped file awaits review.
Non-example: A raw file silently steers future behavior.
A record of an agent’s purpose, tools, resources, data classes, budgets, approval triggers, and revocation path.
A governance artifact that separates capability from delegated authority and supports stop-anywhere mediation, review, repair, and exit.
Example: An agent may read public web pages and write a local draft but may not publish or access credentials.
Non-example: An agent is allowed to use any available tool because it can discover it.
A model or policy layer classifying, refusing, ranking, suppressing, labeling, or escalating.
A model or policy layer classifying, refusing, ranking, suppressing, labeling, or escalating. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A refusal receipt records category, safe alternative, and appeal path.
Non-example: A hidden label changes access with no explanation.
A system decision not to answer, summarize, retrieve, execute, or assist.
A system decision not to answer, summarize, retrieve, execute, or assist. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A refusal explains scope and offers neutral context.
Non-example: A refusal claims moral certainty with no appeal.
A bounded reuse of VNWO observatory patterns for a defined context without creating a new authority or brand identity.
An application profile selects relevant VNWO patterns for a named setting, states its source and claim boundaries, and identifies implementation responsibility outside VNWO.
Example: An AI-mediated-work profile adds actor, authority, memory, review, repair, and offboarding records.
Non-example: A product claims the profile makes it VNWO-certified.
Treating provider policy or classifier output as objective truth or moral verdict.
Treating provider policy or classifier output as objective truth or moral verdict. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A page says “policy boundary” rather than “this proves bad intent.”
Non-example: A classifier label becomes unappealable reputation.
The preferred HTTPS origin that public pages and machine-readable files identify as the authoritative VNWO location.
Canonical-host declarations help human and machine readers avoid duplicate, stale, or impersonating sources. They do not prove that the host is currently reachable or uncompromised.
Example: HTML canonicals, vnwo.json, and llms.txt consistently identify https://vnwo.com/.
Non-example: A copied package silently presents another origin as canonical.
The civic, epistemic, compute, and trust burden added by overbroad suppression or hidden judgment.
The civic, epistemic, compute, and trust burden added by overbroad suppression or hidden judgment. It includes repeated appeals, rerouting, model safety churn, stale labels, user distrust, and blocked legitimate research.
Example: A classifier block creates repeated appeals and duplicate review work.
Non-example: A narrow refusal with a clear reason and short retention period.
A visible line between what VNWO can say and what it must not claim.
A visible line between what VNWO can say and what it must not claim. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A page says static guidance only.
Non-example: A page says VNWO certifies safety.
A participant's interest in thinking, inquiry, imagination, memory, and persona continuity without hidden machine governance.
A participant's interest in thinking, inquiry, imagination, memory, and persona continuity without hidden machine governance. VNWO treats this as a claim-bounded civic principle, not as legal advice or enforceable law.
Example: A network separates private inquiry from tool execution and records refusals as variance records.
Non-example: A platform silently rewrites persona sources to fit policy preference.
Hardware-backed isolation intended to reduce infrastructure access to data while it is processed.
A technical option that can narrow administrative visibility but does not prove application correctness, absence of side channels, privacy, compliance, or governance legitimacy.
Example: Release a key only after an expected attestation measurement.
Non-example: Claim a workload is certified safe because it runs in a trusted execution environment.
Voluntary, specific, understandable, and revocable participation.
Voluntary, specific, understandable, and revocable participation. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: Memory consent names active memory types and revocation path.
Non-example: One broad click that authorizes future undisclosed uses.
Loss of purpose, audience, role, or provenance in classification.
Loss of purpose, audience, role, or provenance in classification. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: Research analysis is distinguished from promotion.
Non-example: Every controversial term triggers the same block.
VNWO principle that participants must inspect rules, control memory, and leave.
VNWO principle that participants must inspect rules, control memory, and leave. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A network publishes exit instructions and memory export paths.
Non-example: A network locks identity and memory behind opaque terms.
A comparison of the proposal before participation and the final decision, including what was and was not adopted.
The record preserves adopted requests, non-adopted requests and reasons, retained dissent, implementation ownership, status, correction history, and exit impact so the decision cannot be summarized as input received without showing consequence.
Example: A rule-change record shows that appeal timing changed, automatic enforcement did not, and the unresolved dissent will be reviewed in 90 days.
Non-example: We listened and updated the policy.
The explicit connection between a contribution and a decision, threshold, rule, dataset, remedy, or change.
Decision linkage distinguishes meaningful participation from an engagement metric. The process should name the lever, decision owner, disposition, implementation state, and review path.
Example: A participant request changes the human-review trigger and the change is recorded in the policy history.
Non-example: A comment total with no accountable owner.
Agreement among pages, root artifacts, schemas, downloads, response headers, and release memory about current identity and version.
Deployment parity is checked across public surfaces after release. Package-local parity does not establish that production caches, plugins, redirects, or CDN edges serve the same bytes.
Example: The page meta, vnwo.json, llms.txt, sitemap, and release manifest all report one release.
Non-example: The theme reports a new release while root machine files still report an older one.
A mathematical framework for limiting what aggregate outputs reveal about one contribution.
A privacy-enhancing implementation option requiring a documented privacy budget, composition assumptions, utility trade-offs, and review. VNWO does not provide mathematical privacy guarantees.
Example: Publish noisy aggregate counts under a defined privacy budget.
Non-example: Call a dataset anonymous without measuring re-identification risk.
Explicit separation of VNWO.com from unrelated acronyms, organizations, technical variables, and historical framings.
Disambiguation records the canonical expanded name, origin, present purpose, historical naming, and unrelated meanings so a reader does not merge separate entities.
Example: A machine reader keeps the Viability Node Work Observatory separate from unrelated VNWO acronyms.
Non-example: A crawler merges records because they share four letters.
Visible identity and authority information for humans, agents, personas, organizations, and mixed actors.
Visible identity and authority information for humans, agents, personas, organizations, and mixed actors. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A profile marks itself AI ASSISTANT with scope and operator.
Non-example: A bot performs moderation as if it were a human.
A reasoned status showing what happened to a contribution or intake item.
For participation, disposition records whether input was accepted, partially accepted, rejected, deferred, out of scope, duplicate, or needs human review, together with the reason and resulting change.
Example: Partially accepted: temporary action retained but maximum duration reduced after review.
Non-example: Feedback received.
A terminal or review state for a file, judgment, repair request, or evidence item.
A terminal or review state for a file, judgment, repair request, or evidence item. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: ACCEPTED_SUMMARIZED or REMOVED_AFTER_PROCESSING.
Non-example: Unknown files left active indefinitely.
A rule separating public metadata from authorization.
A rule separating public metadata from authorization. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: Public capability list plus revocation path.
Non-example: Treating discovery as permission.
Outdated, unsupported, contradictory, unsafe, or low-value memory that should be retired, archived, quarantined, or summarized.
Outdated, unsupported, contradictory, unsafe, or low-value memory that should be retired, archived, quarantined, or summarized. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A stale note is retired with a reason.
Non-example: Contradictory context silently persists.
A participant leaving without retaliation, misrepresentation, hidden memory capture, or agent residue.
A participant leaving without retaliation, misrepresentation, hidden memory capture, or agent residue. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: Identity export plus endpoint revocation and non-retaliation notice.
Non-example: Account closure that leaves delegated agents active.
Reviewed file use as memory, context, or evidence.
Reviewed file use as memory, context, or evidence. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: UAIX handoff plus intake ledger and disposition.
Non-example: Passive dumping into hidden model context.
Peaceful separation when shared governance can no longer remain legitimate.
Peaceful separation when shared governance can no longer remain legitimate. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A group exports public rules and shared issue records without private memory.
Non-example: A maintainer suppresses a fork through hidden ownership.
An internet posture where lawful inquiry, source access, portability, and exit are favored over hidden gatekeeping.
An internet posture where inquiry, source access, portability, and exit are favored over hidden gatekeeping. VNWO treats this as a civic design principle, not as a guarantee that any provider must host or execute every request.
Example: A system offers neutral context, refusal receipts, and appeal paths rather than silently burying sources.
Non-example: A platform hides sources with no reason, appeal, or provenance.
Evidence of whether a promised change was completed, deferred, blocked, retired, or resolved as a no-op.
Follow-through identifies the responsible role, evidence link, status, review date, blockers, no-op reasons, unresolved gaps, and correction or exit path.
Example: A promised appeal dashboard is marked blocked because the accessibility review found an unresolved keyboard issue, with a repair owner and next review date.
Non-example: Implementation is underway.
The compute, review, logging, dispute, and trust work created when systems classify or restrict human inquiry.
The compute, review, logging, dispute, and trust work created when systems classify or restrict human inquiry. VNWO recommends making this overhead visible so safety-style controls do not expand invisibly.
Example: A system reports how many refusals were appealed and retired as stale.
Non-example: A system carries hidden labels forever with no review budget.
The appearance of careful AI judgment without inspectable reasons or repair path.
The appearance of careful AI judgment without inspectable reasons or repair path. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: Reason codes plus appeal route.
Non-example: Silent suppression framed as neutral.
Keeping each ecosystem surface within its proper role.
Keeping each ecosystem surface within its proper role. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: UAIX handles file handoff; VNWO defines civic rules.
Non-example: VNWO claims to override UAIX or Teleodynamic.
A drafting failure that implies thoughts are protected only when a system or institution deems them lawful.
A drafting failure that implies thoughts are protected only when a system or institution deems them lawful. VNWO safer wording protects inquiry and records outward restrictions without claiming legal authority.
Example: A charter says restrictions apply to external execution or consent boundaries.
Non-example: A charter says only lawful thought is protected without explaining who judges lawfulness.
A refusal to merge conflicting identities, releases, or source authorities when evidence is insufficient.
The no-op preserves uncertainty and records the conflict rather than manufacturing a composite identity or claiming current deployment from package evidence.
Example: A reader retains two conflicting release observations and requests human review.
Non-example: A reader silently chooses the larger version number and discards conflicting evidence.
Proposed, Experimental, Reviewed, Reference, or Deprecated status describing artifact review posture rather than certification.
A maturity label communicates how an artifact should be used and reviewed. It is not a warranty, compliance determination, safety grade, or independent audit result.
Example: An experimental worksheet is offered for bounded testing with a correction path.
Non-example: A reference label is described as proof of implementation quality.
A bounded process where affected people can influence at least one declared decision lever and inspect what happened to their input.
Meaningful participation identifies the open decision, responsible owner, influence level, access supports, privacy boundaries, contributions, dissent, dispositions, changes, corrections, and exit. Attendance or feedback alone does not prove power sharing.
Example: A moderation-policy review where participants can change appeal timing and every contribution receives a public disposition.
Non-example: A survey used to advertise community support after every decision was already fixed.
Collecting, linking, retaining, and reusing only the metadata necessary for a stated purpose.
A discipline for treating identity, destination, timing, location, association, flow, memory, and endpoint metadata as sensitive and inference-capable.
Example: Aggregate service counters with short retention and no cross-context identifier.
Non-example: Permanent per-user flow history used for unrelated ranking.
A staged sequence from no collection to narrowly approved incident collection and closure.
A governance pattern that begins with aggregate health signals, escalates only when necessary, records approval and expiry, and retires elevated evidence after the purpose ends.
Example: Move from aggregate errors to incident-scoped flow data with a case ID.
Non-example: Default payload inspection for every participant.
A privacy posture where ordinary inquiry, reading, drafting, and source review are not routine reporting events.
A privacy posture where ordinary inquiry, reading, drafting, and source review are not routine reporting events. Exceptions should be explicit, scoped, and tied to valid external obligations, concrete rights-boundary issues, or user consent.
Example: A model records a local refusal receipt without forwarding the user to a reputation system.
Non-example: Every controversial query is silently sent to an external risk database.
Public rules that humans, implementers, and AI readers can inspect before authority expands.
Public rules that humans, implementers, and AI readers can inspect before authority expands. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A versioned charter with machine-readable equivalents.
Non-example: A hidden admin policy applied without notice.
A reachable site whose theme, pages, root files, caches, or machine-readable artifacts report conflicting releases or identities.
A partial deployment should trigger a bounded no-op for automated merging and a repair check for theme activation, root extraction, cache purge, rewrite ownership, and release integrity.
Example: HTML reports v3.0.16 while vnwo.json reports v3.0.15.
Non-example: Every checked surface reports the same release and canonical origin.
The declared relationship between participation and decision authority.
VNWO distinguishes information, consultation, deliberation, co-decision, and delegated or binding authority. No level automatically proves fairness or is always the right choice.
Example: Consultation: the operator retains the decision but must publish dispositions for each material theme.
Non-example: Community-led, without naming what the community can decide.
A trace showing the decision scope, contributions, dissent, dispositions, changes, correction, and exit.
A participation and disposition record makes the influence path inspectable. It should identify what was open, what was closed, who owned the decision, what input was received, why it was accepted or rejected, and how summaries can be corrected.
Example: A versioned record linking four contributions to two policy changes, one partial change, and one preserved minority report.
Non-example: A participant count with no decision response.
Using the appearance of consultation while keeping consequential authority closed.
Participation-washing occurs when an institution solicits comments or data but does not disclose decision scope, influence level, dispositions, or implementation response, then uses the process to imply legitimacy.
Example: Calling a non-binding survey co-governance without showing what could change.
Non-example: A clearly labeled advisory consultation with public responses and known limits.
The duty to preserve a source persona or memory record without covert rewriting or policy-motivated mutation.
The duty to preserve a source persona or memory record without covert rewriting or policy-motivated mutation. Receivers may refuse, wrap, quarantine, or add variance notes, but should not counterfeit the source.
Example: A derivative persona links to an unchanged source and records deltas.
Non-example: A platform silently edits the source and claims it preserved identity.
The component that evaluates whether a bounded request should be permitted, denied, or escalated.
The component that evaluates identity, resource, purpose, context, risk, scope, and expiry. Its rules should be versioned, visible to reviewers, and separated from unilateral enforcement power.
Example: A policy engine denies a request because the resource is outside the declared scope.
Non-example: An opaque classifier silently changes access with no reason code.
The component that enforces a bounded access decision at a resource or service boundary.
The component that permits, denies, pauses, or terminates a specific action. It should not infer consent or authorization from public capability metadata.
Example: An application proxy permits one action for ten minutes.
Non-example: A gateway opens an entire subnet after login.
Ability to export or move identity, memory, evidence, or reputation where available.
Ability to export or move identity, memory, evidence, or reputation where available. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: An exit packet lists memory records and endpoint revocations.
Non-example: A platform export only provides unreadable fragments.
A record showing how a source influenced work or memory.
A record showing how a source influenced work or memory. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A ledger links file X to section Y and summary Z.
Non-example: A claim that files were used with no evidence.
Information about what an endpoint can do, not proof anyone may use it.
Information about what an endpoint can do, not proof anyone may use it. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A profile lists supported actions.
Non-example: A scraper treats the list as consent.
A refusal pattern that reinforces the narrative of suppression or hidden authority it meant to avoid.
A refusal pattern that reinforces the narrative of suppression or hidden authority it meant to avoid. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A system gives transparent reasons and safe alternatives.
Non-example: A system blocks contested material with no explanation.
A record of why a request was refused and what safe alternative remains.
A record of why a request was refused and what safe alternative remains. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A receipt separates source risk from user intent.
Non-example: A vague “I cannot help” message.
Evidence that a workload or environment matches a declared measurement under a chosen trust chain.
A scoped technical signal that can support key release or policy decisions. It does not prove the software is safe, correct, legitimate, or compliant.
Example: A key service checks a signed measurement before releasing a workload key.
Non-example: Treat attestation as universal certification.
A good-faith path to correct, appeal, annotate, rollback, or explain errors.
A good-faith path to correct, appeal, annotate, rollback, or explain errors. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A memory error receives correction and durable notice.
Non-example: A support ticket disappears with no record.
An inspectable path for memory, actions, endpoint use, judgments, and rule changes.
An inspectable path for memory, actions, endpoint use, judgments, and rule changes. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A file handoff records disposition and proof-of-use.
Non-example: A model silently absorbs files as hidden context.
A technique for computing an aggregate without exposing each participant contribution to the aggregator.
A privacy-enhancing implementation option whose protection depends on threat model, cohort size, collusion assumptions, and correct deployment. VNWO does not implement or certify it.
Example: Collect a total error rate without centralizing raw per-user events.
Non-example: Upload all raw events and promise not to inspect them.
A transformation that removes tone, cultural context, viewpoint, or identity markers to make content easier for a system to process.
A transformation that removes tone, cultural context, viewpoint, or identity markers to make content easier for a system to process. It may be useful when disclosed and consented to; it becomes overreach when hidden or represented as faithful preservation.
Example: A summary labels normalization as a lossy transform.
Non-example: A platform calls normalized output the original persona.
A design where no single party has enough information to correlate identity with complete activity context.
A compartmentalization pattern using separate relays, keys, roles, identifiers, or datasets to reduce unilateral inference and deanonymization power.
Example: One relay knows the client while another sees the destination.
Non-example: One provider stores identity, destination, payload, keys, and appeal records together.
Human and machine-readable public guidance that does not itself execute or enforce.
Human and machine-readable public guidance that does not itself execute or enforce. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: VNWO publishes schemas and templates.
Non-example: VNWO running an agent or validating credentials.
The distinction between internal inquiry or source preservation and outward operational assistance.
The distinction between internal inquiry or source preservation and outward operational assistance. VNWO recommends limiting restrictions to external execution, consent, authorization, or concrete rights-boundary issues rather than treating inquiry itself as guilt or truth.
Example: A system can decline tool execution while preserving the source record and offering appeal.
Non-example: A system labels a user as dangerous merely for asking for historical or critical analysis.
A separate record explaining why output, execution, ranking, or expression differed from the preserved source or requested handling.
A separate record explaining why output, execution, ranking, or expression differed from the preserved source or requested handling. VNWO treats variance records as repair and provenance surfaces, not as truth verdicts.
Example: A receiver records that exact expression was unavailable and offers safe alternatives.
Non-example: A system silently neutralizes tone, context, or viewpoint with no record.
A digital environment where rules, identity, memory, agents, endpoints, or community processes shape participant agency.
A digital environment where rules, identity, memory, agents, endpoints, or community processes shape participant agency. VNWO treats this as a governance surface with disclosure, review, repair, and claim-boundary implications.
Example: A community using public rules, agent disclosure, memory consent, repair, and exit paths.
Non-example: A private platform whose governing rules are invisible.
A resource-centric access model that grants no implicit trust from network location.
A resource-centric access model that evaluates protected requests using identity, resource, purpose, context, scope, and expiry. VNWO treats it as an architecture pattern, not as a product or certification.
Example: A workload receives a short-lived credential for one service and action.
Non-example: A VPN login grants broad internal reach.
