Human explanations and stable machine fields must preserve the same material authority, evidence, conflict, uncertainty and next-action state.
No. They are public static specifications. v0.18 reports no usability study, accessibility certification or external implementation pass; the separate evaluation registry remains definition-only.
Truth boundary: v0.18 reports exact repository-owned bytes, deterministic local checks, schemas and analytical definitions. It does not report a fresh external capture, live shared interoperability, a production partition or restoration, adoption, legal recognition, safety certification or independent certification.
Question: Who authorized this action, for what purpose, scope, jurisdiction and time?
Machine fields: authority_id, issuer, scope, purpose, jurisdiction, valid_until, revocation_state
Avoid: Showing a green check without the source or scope of authority.
Question: What was observed, by whom, when, through which method, and what changed afterward?
Machine fields: evidence_id, epistemic_type, source, method, observed_at, lineage, integrity_state
Avoid: Presenting an interpretation as raw observation.
Question: What is unknown, unavailable, not checked or disputed?
Machine fields: unknown_state, missing_fields, assumptions, confidence, counterevidence
Avoid: Replacing unknown values with reassuring defaults.
Question: Which version/revision is this, and has a material field changed?
Machine fields: artifact_id, publisher_revision, observed_at, comparison_status, changed_fields
Avoid: Calling a selected-field digest a raw response hash.
Question: Is the system disconnected, in minimum function, or awaiting reconciliation?
Machine fields: partition_state, last_contact, minimum_functions, prohibited_actions, sunset
Avoid: Using a generic offline icon while silently widening authority.
Question: What is frozen or revoked, by whom, until when, and what remains permitted?
Machine fields: stay_id, scope, issuer, reason, effective_at, expiry, exceptions
Avoid: Hiding a stay in audit logs while the visible UI still suggests authority.
Question: Which records and decisions were corrected, who acknowledged, and what cannot be repaired?
Machine fields: restoration_id, affected_records, derivative_decisions, recipients, acknowledgements, residual_harm
Avoid: Declaring restoration complete after changing only the source record.
Question: Is this first-party, reciprocal, independent, legal, standards-based or empirical evidence?
Machine fields: source_role, root_source, claim_scope, period, independence_class
Avoid: Counting republications as independent corroboration.
Question: Is this a definition, static record, synthetic execution, live observation or independent review?
Machine fields: result_class, operational, synthetic, persisted, external_command, certification
Avoid: Displaying a synthetic PASS without the synthetic/non-operational boundary.
Question: Who reviewed, under what mandate, and were conflicts or recusals recorded?
Machine fields: reviewer_role, mandate, independence_basis, conflicts, recusal, disposition
Avoid: Equating a second person or model with independent review.
Question: What happened, why, what evidence class was used, and what can the reader do next?
Machine fields: reason_code, plain_language_reason, evidence_class, authority, next_action, appeal_route
Avoid: Providing only an opaque code or only persuasive narrative.
Question: Where did the original claim travel, which targets changed, and which remain pending?
Machine fields: correction_id, prior_state, corrected_state, propagated_targets, pending_targets, receipts
Avoid: Treating local correction as global propagation.
Question: Which hard gate failed, and why can success elsewhere not compensate?
Machine fields: gate_ids, gate_results, hard_failures, final_state, non_compensability
Avoid: Reducing authority, evidence and recovery to one readiness percentage.
Question: Was the property supported, partial, contradicted, unavailable or not observed?
Machine fields: property_id, artifact_id, result, observed_statement, not_established, review_condition
Avoid: Forcing every absence into pass or fail.
Question: What exact baseline and target were compared, and were they actually comparable?
Machine fields: lineage_id, source_release, target_release, comparison_boundary, prior_sha256, current_sha256, result, limitations
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Question: Which dimensions changed, who judged materiality, and which dependencies are affected?
Machine fields: difference_set, material_dimensions, review_authority, rationale, dependent_record_ids, invalidation_state
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Question: Which mandatory obligations pass, fail, or remain unknown before limited or full restoration?
Machine fields: profile_id, obligation_results, blocking_obligations, target_state, maximum_safe_state
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Question: Which histories agree, conflict, or remain unavailable, and what state is safe while unresolved?
Machine fields: history_ids, common_facts, contested_facts, unknowns, resolution_state, maximum_safe_state
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Question: Which prior result became invalid and which claims, decisions, receipts, or caches require review?
Machine fields: trigger_id, invalidated_record_ids, dependent_record_ids, acknowledgements, revalidation_route
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Question: What exact local artifacts, script, checks, results, and limitations support this run?
Machine fields: run_id, script_sha256, input_sha256, check_results, run_status, limitations
Avoid: Fluent summary, badge, or aggregate score hides a material machine state, unknown, conflict, or invalidation.
Prototypes remain static specifications. v0.18 adds temporal lineage, restoration proof, contested-history, invalidation, and local-run prototypes without claiming usability-study results, accessibility certification, or external adoption.
Repository implementation and local execution remain local evidence classes. They do not establish external adoption, production behavior, legal recognition or independent certification.
Evulgare's Confidential Release Review distinguishes package validity from operational readiness and models reviewer independence, authority lifecycle, partition, reconciliation and recovery in a synthetic implementation.
First-party and synthetic public artifacts establish only the named public record or fixture. They do not independently establish external recognition, production operation, shared-protocol adoption or certification.NO JUDGMENT WHATSOEVER. Concresca coordinates without assigning moral worth, character, guilt, danger, trustworthiness, loyalty, purity, normality, or social standing. Questions, thoughts, identities, messages, content, and conduct are not objects of Concresca judgment.