Level 1 — Aware

At Level 1, you understand the territory but have not yet entered it. The map exists; no footprints do.

What Level 1 Feels Like

Level 1 is the level of genuine comprehension without systematic practice. A practitioner at Level 1 can explain the difference between an assertion and a claim, articulate why evidence quality matters, and describe what a reasoning chain is for. They may have read this documentation, attended a workshop, or worked through a sample claim. What they have not yet done is apply VERA to claims that matter — in their actual work, on their actual decisions.

This is not a failure state. Level 1 is a genuine achievement over Level 0 (no awareness at all), and it is the necessary precondition for everything that follows. You cannot develop practice before developing understanding. What distinguishes Level 1 from Level 2 is not knowledge — it is application.

For organizations, Level 1 typically means that a handful of people understand VERA and may be advocating for its adoption, but no institutional practice has been established. There are no claim records, no evidence sets, no verification records in the organizational knowledge base. VERA is a future state, not a current one.

The Six Domains at Level 1

Evidence

At Level 1, the four-tier evidence quality rating (Primary, Secondary, Tertiary, Testimonial) is understood conceptually. The practitioner can correctly classify a given evidence item when asked to — a raw dataset is Primary, a peer-reviewed synthesis is Secondary, a textbook summary is Tertiary — but this classification does not happen as part of normal work. Evidence items are not rated in practice; they are simply used.

The concept of evidence independence is understood: multiple news articles citing the same press release are not independent evidence. But source collapse (the error of treating them as independent) continues to occur in practice because no process exists to check for it.

The prospective search plan — documenting what evidence you’re looking for before you look, so that absence can be noticed and recorded — is understood as a principle but not applied. Searches happen; they are not planned and documented.

The concept of absent evidence — the evidential significance of what you didn’t find — is understood at Level 1. It is not yet recorded.

Observable evidence that a domain is at Level 1:

Staff can correctly rate evidence items when asked to do an exercise
No claim records in the organizational knowledge base include evidence quality ratings
When asked “what evidence supports this claim?” practitioners can retrieve evidence but cannot demonstrate a systematic search process

Reasoning

At Level 1, the distinction between a reasoning chain and a conclusion is understood. “We concluded X because Y” is recognized as an incomplete statement — it omits the logical steps connecting Y to X, the inference type used, and the assumptions the argument depends on. The practitioner understands that this incompleteness is a problem, not a stylistic choice.

The four inference types (deductive, inductive, abductive, analogical) are understood as distinct. The practitioner can identify which type is being used when one is pointed out.

What does not yet exist is the discipline of writing reasoning chains. When producing a conclusion, the practitioner typically produces the conclusion and perhaps a summary of supporting considerations — not a step-by-step argument with labeled inference types, documented assumptions, and intermediate conclusions. This is not evasion; it is habit. The habit of explicit reasoning chains develops in Level 2.

Observable evidence that a domain is at Level 1:

When asked to explain their reasoning, practitioners provide conclusions and supporting observations, not explicit reasoning chains
Staff recognize reasoning gaps when shown examples but do not catch them in their own work
No claim records in the organizational knowledge base include step-by-step reasoning chains

Verification

At Level 1, the concept of verification — distinct from agreement, distinct from review, distinct from the original claimant checking their own work — is understood. The practitioner understands why independence matters: the verifier’s job is to look for failures, not to endorse conclusions.

The Verification Protocol is understood at a high level. The practitioner knows it involves five phases and that verification produces a formal record. They have not applied it to a real claim.

Critically, at Level 1 there is often still some conflation between “we reviewed this and agree with it” and “this has been verified.” Verification in VERA means something specific: evaluation against explicit criteria by someone other than the claimant, producing a formal record. Informal agreement is not verification, however carefully the agreement was reached.

Observable evidence that a domain is at Level 1:

Staff can describe the Verification Protocol phases from memory or with brief reference
No verification records exist in the organizational knowledge base
When asked how a key organizational claim was verified, the answer describes agreement, review, or consensus — not a formal verification process

Governance

At Level 1, VERA is known to enough people that the conversation about adoption is possible. Someone — typically the person who encountered VERA and brought it to the organization — understands it well enough to advocate for it. Leadership is aware that VERA adoption has been proposed, even if they have not yet made a decision.

What does not exist is any formal mandate, budget, ownership, or policy. VERA adoption, to whatever degree it exists, is voluntary. No one is required to use VERA formats, no resources have been allocated to VERA implementation, and no one has formal responsibility for VERA practice.

The absence of governance at Level 1 is expected and appropriate. You do not need governance structures for a practice that hasn’t been demonstrated to work in your context. The role of Level 1 Governance is to create the conditions for Level 2 exploration: enough institutional awareness that individual champions can experiment without being obstructed.

Observable evidence that a domain is at Level 1:

At least one person can articulate the VERA framework clearly to leadership
No VERA policy, mandate, or formal ownership exists
VERA has been discussed in at least one organizational forum (team meeting, planning session, working group)

Sovereignty

At Level 1, the concept of epistemic sovereignty — the capacity to access, inspect, challenge, and ultimately own the knowledge you act on — is understood. The practitioner can describe what it would mean for an organization to lack data sovereignty (evidence locked in a vendor system that could lapse) or reasoning sovereignty (decisions made on AI-generated conclusions with no visible reasoning chain).

What has not yet happened is assessment: no one has systematically evaluated which of the five Sovereignty Principles the organization currently meets, which it partially meets, and which it violates. The sovereignty landscape is understood conceptually; it has not been mapped for the current context.

This absence of assessment is the primary Level 1 Sovereignty characteristic. You cannot remediate gaps you haven’t identified, and you cannot identify gaps without assessment. The assessment itself — not the remediation — is what defines Level 2 Sovereignty progress.

Observable evidence that a domain is at Level 1:

Staff can describe each of the five Sovereignty Principles accurately
No formal sovereignty assessment has been conducted
Key questions about the current state — “Can we export all our evidence? Can any stakeholder trace a claim’s reasoning chain? Can anyone formally challenge a verified claim?” — have not been formally answered

Integration

At Level 1, VERA is conceptually understood as something that would complement existing work — that claim documentation would improve knowledge management, that evidence rating would improve decision-making quality, that verification records would improve audit capability. The connection between VERA and existing workflows is apparent.

What does not exist is actual integration. VERA has no presence in the organization’s tools: not in the wiki, not in the project management system, not in the decision log, not in the knowledge base. When work happens, it happens in the organization’s native processes. VERA notation, templates, and formats are theoretical.

The absence of integration at Level 1 is not a problem — it is the expected state. Integration before practice is premature. The Level 1 Integration goal is simply to identify the workflows where VERA would add value, so that integration can be planned during Level 2 exploration.

Observable evidence that a domain is at Level 1:

No VERA notation, templates, or formats appear in organizational tools
Staff can identify the workflows where VERA would be most valuable
No claim registry exists; no decision has been made about where it would live

Signals That Confirm Level 1

Across all six domains, the following are strong signals that an individual or organization is genuinely at Level 1 (and not lower or higher):

Reading this documentation feels like recognition, not confusion — the concepts are intelligible and coherent
Reviewing past claims or decisions reveals obvious gaps (absence of evidence documentation, implicit reasoning) that were not obvious before learning VERA
The first attempt to document a claim using VERA formats feels awkward and effortful — because the habits are not yet formed
Conversations about VERA adoption produce real engagement (not dismissal and not immediate full buy-in) — the framework is credible but not yet proven in context

What Does Not Qualify as Level 1

Below Level 1:

VERA is completely unknown
The person can describe what “evidence” means in everyday language but not the VERA-specific distinction between evidence tiers
“Verification” means spell-checking or review for consistency, not epistemic evaluation against criteria

Mistaken self-assessment at Level 1:

“We already do this” — most organizations that feel they already verify claims are performing agreement, review, or consensus, not VERA verification. The key question: do verification records exist? If not, you are at Level 1 or below in the Verification domain, regardless of how carefully decisions are made.
“We just need to formalize what we’re doing” — this is sometimes true (Level 2 organizations often do have informal VERA-like practices that can be formalized) but is frequently an overestimate. Formalizing a practice reveals that it was less consistent than it felt.

Moving from Level 1 to Level 2

The transition from Level 1 to Level 2 does not require organizational approval, budget, or mandate. It requires one thing: applying VERA to a real claim.

Not a practice claim. Not a simplified example. A claim that actually matters — one that will be used to inform a real decision, support a real argument, or guide a real action. This is what converts understanding into practice and reveals the inevitable gap between the two.

Concrete steps:

Select a claim. Choose one claim from your current work that is significant enough to matter. Compound it if needed. State it precisely (Verification Protocol Phase 1).
Assemble evidence. Write a prospective search plan first. Then conduct the search. Rate what you find. Document what you don’t find. (Phase 2)
Build the reasoning chain. Write it step by step. Label each inference type. Document the assumptions you’re making. (Phase 3)
Verify it. Ask someone else — with at least some independence from the claim — to evaluate it against the criteria in Phase 4 of the Verification Protocol.
Create a record. The claim record, with its evidence set, reasoning chain, and verification record, is your first documented VERA artifact. It is also your first evidence that Level 2 practice is underway.

The first full VERA claim will take significantly longer than expected. This is normal. The second will be faster. By the fifth, the format will have become familiar enough that the cognitive effort shifts from “remembering the format” to “doing the substantive work” — which is where it belongs.

Level 1 Self-Assessment Checklist

Use this checklist with specific evidence for each item — not general impressions.

Understanding (all must be Yes for Level 1):

I can define Claim, Evidence Item, Reasoning Chain, and Verification State without looking them up
I can correctly classify a given evidence item into the four-tier quality scale
I can describe the five phases of the Verification Protocol at a high level
I can name and describe all five Sovereignty Principles
I understand the difference between verification and agreement/review/consensus

Practice (all must be No for Level 1 — if any are Yes, you may be at Level 2):

I have documented at least one claim using the full VERA format including evidence set and reasoning chain
I have created at least one Verification Record
Evidence quality ratings appear in my organization’s working documents
A claim registry exists in my organization, even informally

Position (confirms Level 1 vs. Level 0):

I have read at least the Foundations section of this documentation
I can explain VERA to a colleague who has not encountered it before
I can identify at least two claims in my current work that would benefit from VERA documentation

Proceed to Level 2 — Exploring to understand what the first steps of systematic practice look like and how to navigate common early challenges.