Choose the source type
| Add source tab | Use it for | Behaviour before locking |
|---|---|---|
| Local Repositories | A Git repository or local folder | Read in place; a Git repository is recognised automatically |
| Knowledge Artifacts | PDFs, API specifications, CSV, Markdown, archives, and other approved files | Inspected and classified by format |
| Add Tacit Knowledge | Decisions, operational knowledge, ownership, and context supplied by a person | Stored as an attributed Markdown note |
A local item that is not recognised as a Git repository is treated as a knowledge artifact. On macOS, files and folders may require separate picker actions because the operating system cannot offer both in one picker.
Add local evidence
1. Open the harness and choose Sources → Add source. 2. Choose Local Repositories or Knowledge Artifacts. 3. Select the repository, folder, or file on this machine. 4. Review the detected type and add source-specific context where it will help interpretation. 5. Repeat until the evidence boundary is complete, then review it before locking.
Local evidence is read in place while you prepare the boundary. It is copied into the harness when you lock the source list.
Add attributed tacit knowledge
1. Choose Add Tacit Knowledge. 2. Record the knowledge as a focused note. 3. Attribute it to the person or authority that supplied it. 4. Explain its scope and when it was true. 5. Save it and review it alongside the other sources before locking.
Tacit knowledge is intentionally a weaker evidence tier than parsed declarations or direct observations. Attribution preserves its value without presenting human recollection as verified system behaviour.
Security boundary
Adding a local source does not modify the original repository or artifact. Locking creates the immutable evidence boundary used by the harness. If the wrong evidence was selected, create a new harness rather than altering the locked boundary.