Object Authority / Method

EchoNet uses a publication method before private lab work becomes public text.

The chain is:

1. private project record
2. source boundary
3. public-risk filter
4. public claim
5. unknowns left open

The method is used here because it worked on this corpus. It is not offered as universal doctrine.

Name The Object

A page starts by naming the object it is about. The named object is kept separate from nearby evidence, interpretation, and new synthesis.

This prevents a public page from replacing the thing it is supposed to describe.

Set The Source Boundary

Source material can include repos, handoffs, manifests, route indexes, forensic reports, diagnostic ledgers, experiment notes, failure records, method records, and build notes.

The boundary asks what the source can actually support. A source can show that an artifact existed, that a problem recurred, that a trap appeared, or that a method survived repeated use.

It does not automatically authorize publishing the underlying private material.

Filter The Claim

The public filter is contextual, not token-based.

A term can be public when it names a broad record class. The same term becomes unsafe when it exposes a private mechanism, a platform-specific integration, a legal-risk surface, a private path, or an unfinished architecture.

State The Public Claim

A public claim is narrow by default. It says only what can be carried without private internals or unsupported completion.

Claims that need private details are not upgraded into public narrative. They are narrowed, removed, or held as open.

Leave Unknowns Open

Unknowns are part of the record.

If the source does not establish a cause, status, or general rule, the page does not close it by tone. It leaves the point visible as unresolved.