Methodology

Ektar

The operating methodology behind everything on this site. One rule, applied without exception: every consequential claim carries its status, and no claim ships without a checked receipt.

The claim tiers

• verifiedSeen in a primary source or a checked trace — a tool output, a receipt ID, a log line with a timestamp.
• inferredFollows from verified facts, with the reasoning shown. The inference is labeled; it never wears the clothes of a measurement.
• guessedA working assumption, marked as one. Useful for planning, worthless as evidence.
• unknownExplicitly preserved. An unmarked gap becomes a lie by the next session; a marked one stays a question.

Why it matters

Configuration expresses intent; only a trace establishes behavior. A system that cannot tell you how it knows what it claims is not a system — it is a story. Ektar is the discipline of keeping the two apart: provenance, authority, and review date on every consequential claim, and the unknown kept visible instead of paved over.

Ektar is a practice, not a product. It has no repository and no release — it is how the repositories and releases on this site were made.