Cortex
A question becomes a grounded draft with source material a person can inspect.
- Question
- Retrieved source
- Draft
- Citation
- Human decision
Platform
Two products. One rule: important output should be inspectable.
Cortex preserves evidence around knowledge. Canopy Host preserves evidence around software delivery. They solve different problems and remain independently usable.
What this does not mean
- Cortex does not require Host or Forest.
- Host does not require Cortex.
- Forest is Host's execution layer, not a product plan.
- Shared principles do not mean shared customer data.
Evidence loops
The record should survive the action.
Canopy Host
A software change becomes a known artifact, a release, a deployment, and a reported runtime state.
- Commit
- Pipeline
- Build
- Immutable artifact
- Release
- Deployment
- Observed state
Why they belong together
Less reconstruction. Fewer unsupported assumptions.
Teams lose time reconstructing a support answer from scattered documents, or a production change from dashboards, build logs, and memory. Cortex and Host make different evidence chains available in the systems where work happens.
Cortex helps a reviewer ask, “What supports this answer?” Host helps an operator ask, “What was built, promoted, deployed, and observed?” Neither answer should depend on a confident summary or a successful command alone.
Engineering evidence
Relationships, not isolated records.
The Engineering Graph is a preview, opt-in Host capability. It follows relationships between commits, pipelines, builds, artifacts, releases, deployments, and environments.
Questions it is designed to reduce
- Which build produced this artifact?
- Which commit produced that build?
- Which environments are running it?
- What followed from this change?
Its purpose is to make those relationships inspectable, not to sell a graph visualization.
Direction
A common evidence model, not yet one unified product experience.
Over time, Canopy is building toward a world where a human or agent can reason across company knowledge and engineering reality: what changed, what is running, which artifact and commit produced it, and what documentation explains the decision.
Today, that complete cross-product experience is not shipped. Cortex and Host remain separate products. The shared design principle is real; the fully joined operational-answer experience is direction, not a promise.