Find what your software can actually do. Give AI access without giving it the whole software surface.
Harvester reads existing source, recovers bounded computational capabilities, keeps the supporting evidence attached, and lets people review what should become AI-callable before it enters an agent tool surface.
Source first.
Review before AI.
The useful question is not whether a repository contains functions. It is what bounded computation can actually be recovered, what source supports that claim, what interpretation a reviewer is willing to stand behind, and what is safe to expose under an explicit invocation contract.
Recover bounded mechanisms from source without treating discovery as semantic truth.
Attach a proposed meaning to exact source evidence and require a human review decision.
Expose only active reviewed publications through stable AI-facing contracts.
When source moves, show which previously reviewed understanding needs attention.
These states are intentionally not synonyms. Successful recovery does not by itself establish meaning, safety, applicability, or authority.
Codebase Harvest
A bounded engagement to discover what useful computation already exists inside a repository and show exactly what supports each claim.
Recover. Review. Decide what should become usable.
Start with one repository or bounded code area. Harvester recovers supported abilities, preserves source coordinates and mechanism evidence, and separates what was found from what it might mean. Review the candidates together. Where appropriate, establish runnable publications that AI can search, describe, inspect, and invoke without loading the whole repository into a model’s tool surface.
Private/single-tenant deployment remains the appropriate posture for current product engagements.
AI access without losing provenance.
Harvester supports a capability gateway where AI can search, describe, inspect provenance, and invoke active reviewed publications. The gateway keeps the model-facing tool surface stable while the underlying reviewed capability set changes.
Search reviewed publications instead of guessing from file names or repository prose.
Read the bounded meaning, inputs, outputs, and current standing before invocation.
Trace a published ability back to the mechanism and review evidence that support it.
Execution remains constrained by the published contract rather than arbitrary repository access.
What Harvester does not collapse.
Source recovered is not semantic interpretation. Semantic interpretation is not safe execution. Safe execution is not review. Review is not publication. Publication is not universal applicability or authority.