Credentials without inflated personal fog.
The credentials surface explains what is explicitly substantiated on-site and what stays outside the current public scope.
This page is not filled with generic claims. It is a controlled bridge between public statements and more precise proof carriers.
In Batch 6, the proof packet landing acts as the core public evidence carrier. Later phases may add broader credential and downloadable surfaces.
Credentials stay scoped to public proof
Credentials explain what the public site can substantiate now. The page remains a static framing surface, not a credential database, gated proof flow, or private file-delivery layer.
References
Move from credential framing into reference context and public proof relationships.
Proof packets
Use packets as the primary public carrier for bounded evidence relationships.
Dropie public proof packet
Use the current packet as a concrete public credential marker tied to evidence and download metadata.
Evidence metadata
Review the public evidence index without exposing raw evidence or storage internals.
Redacted evidence marker
Check the public evidence page that names redaction status and proof class without raw files.
Download metadata
See metadata-only download records while direct file delivery remains out of scope.
Public brief metadata
Inspect the current metadata-only brief without exposing bucket names, storage paths, or private delivery internals.
Search trust surfaces
Find credentials, references, packets, evidence, and download metadata through the static public index.
What a credential means here
A credential is a public trust marker: it tells readers what the site can substantiate and where the substantiation lives, without exposing access material or private proof flows.
Credential markers
Scoped packet
The packet carries the bounded public claim and links to the evidence and download metadata that support it.
Redaction status
Evidence metadata tells readers whether the public record is redacted, heavily redacted, or summary-only.
Metadata-only download
Download metadata can be inspected publicly while the direct delivery layer remains absent.
Attribution boundary
Credential pages do not publish private testimonial consent details, client records, or security credentials.
- Public attribution belongs on this site only when the source fields are deliberately public.
- Secret credentials, tokens, cookies, and write-token-only data never belong in this surface.
Trust graph
Credential marker
The fixed page names what can be publicly substantiated without becoming a private credential store.
Reference context
References explain how public claims should be read before a reader follows packet evidence.
Search entry
Search keeps credential language discoverable while exposing only safe display and route fields.
Credential boundary
- The word credentials here means public trust markers, not secret keys, tokens, or access material.
- No new credential document type, authentication flow, or browser-side Sanity read was added.
- Private storage, direct downloads, and write-token-only data remain outside the public contract.
Frequently asked questions
Is everything publicly accessible?
No. Some supporting material remains redacted or will later be gated.