Axis 1
Source class
Authority · Professional · Documentary · Representation · Inference
Who or what is speaking in the cited artifact.
Site Evidence Protocol · version 1.0
The Protocol governs how a Site Evidence Record is scoped, sourced, reviewed, released and revised. It prevents a clean transcription from being mistaken for site applicability, gate closure or a professional conclusion.
Verified means GridVision obtained an eligible source artifact and a second reviewer confirmed accurate transcription at the cited location. It does not establish truth, currentness, site applicability, legal compliance, engineering feasibility, approval, capacity or gate closure.
Six independent axes
Axis 1
Authority · Professional · Documentary · Representation · Inference
Who or what is speaking in the cited artifact.
Axis 2
Verified · Unverified
Whether an eligible artifact was obtained and its transcription received the required second check.
Axis 3
Applies · Does not apply · Unresolved
Whether the statement applies to the locked site, load, milestone and purpose.
Axis 4
Not requested · Approved to send · Sent · Received · No response as of [date] · Filed
What has happened in the relevant factual-inquiry or formal-determination workflow; Filed requires formal acceptance and an identifier.
Axis 5
Open · In progress · Waiting on external party · Blocked · Closed
The state of a defined gate against its explicit closure criterion.
Axis 6
Reviewed by counsel · Reviewed by PE · Not professionally reviewed · R0 · R1 · R2
Review and permitted reliance are separately bounded to the exact module, scope, artifact, party, purpose and date stated in the package.
Independent fact flags
Conditional · Conflicted · Expired may coexist with a verified transcription. They do not become a separate axis or disappear when the source text is accurately copied.
Required separations
Two outreach tracks
01
Asks whether a record exists, requests a copy or link, and records its date, identifier or stated workflow status. It does not ask an Authority to apply law or policy to a parcel.
02
May affect legal rights, notice, timing or appeal. Parcel-specific legal conclusions are reviewed and submitted in the client land-use counsel’s name. GridVision does not initiate them; it may only organize and track the resulting record.
A workflow status of Filed is used only when a formal submission has been accepted and an identifier exists. A sent message, received email or elapsed date does not meet that definition.
Gate closure
Every gate is defined before work begins with a closure condition, the artifact or written fact that will satisfy it, an owner, dependencies and any required counsel or engineering review. If the evidence has not been obtained and checked, the gate remains open, in progress, waiting or blocked as applicable.
Nonresponse
It does not prove capacity, approval, compliance, applicability or gate status. The open dependency, request date and next permitted action stay visible in the Record and Plan.
Version control
The type of change determines the revision path. Each new artifact preserves the previous release and states what changed.
Reliance levels
Public-source educational example only. No client, confidential material, client-specific outreach or reliance.
Bound to the named site, load, milestone, purpose, users and as-of date. Authorized viewers may inspect but may not rely.
Unavailable. It is not offered under the current product and responsibility structure.
A GridVision signature identifies the signer, scope, date, material source traceability and execution of the stated Protocol, subject to disclosed limitations, exceptions and protocol deviations. It does not convert the Record into a legal or engineering opinion and does not prove readiness, capacity, legal compliance, approval or energization.
Qualification first
We will first determine whether the site, milestone and cross-workstream dependency fit the current Northern Virginia scope.
Submitting a request is not an engagement or site analysis. A bounded qualification conversation is scheduled only after the limited entity, E&O, counsel-notice, conflict and secure-workspace controls pass. No proposal, signature or payment is accepted until the full commercial gate passes. Controlled production intake and Identity Lock additionally require a signed SOW and settled payment. SER/Plan evidence assembly and Baseline production, Authority outreach, and R1 artifact work begin only after Day 0 is confirmed in writing.