Artifacts

Ogoron writes outputs into a dedicated artifacts directory inside the target repository:

.ogoron/

This section documents the artifacts that matter for daily work.

Directory layout

Typical structure:

.ogoron/
  configs/
  for-human/
  keep-git/
  .meta/

• configs/ — configuration files for the repository
• for-human/ — human-readable outputs (reports, editable XML documents)
• keep-git/ — merge-friendly registries intended for commit
• .meta/ — private runtime data (logs, databases, internal evidence)

What humans typically edit

Most artifacts are generated and do not require manual edits.

Two artifact types are designed for human edits:

• UI test cases (TestCaseXML) — the specification used to generate UI autotests
• Heal conflicts (heal_conflicts.xml) — human verdicts that unlock automated fixes

See:

• UI test cases (editable)
• Heal conflicts (editable)

What to ignore

Many files under .ogoron/for-human/ are intermediate reports and diagnostics.

If an artifact is not listed under “What humans typically edit”, it is usually safe to treat it as read-only.