PROJECT / 24-017Environmental command centre
72% report readyConnected work
EvidenceStateSurface water42 source links 3 gaps
Biodiversity67 source links Reviewed
Noise & vibration31 source links2 in review
Aboriginal heritageRestricted libraryNamed access
Evidence coverage84%
Connected Needs review
Requirements remain connected to their evidenceChange can be traced across disciplines and reportsProfessional review remains explicit
Fragmented infrastructure
Every broken handoff becomes project risk.
Environmental professionals already know how to interpret complex evidence. The risk comes from making them reconstruct the project every time work moves between a document, spreadsheet, inbox, discipline or phase.
- 01
Requirements are interpreted more than once.
- 02
Evidence becomes detached from conclusions.
- 03
New information creates invisible downstream change.
- 04
Reviews happen without a shared source trail.
- 05
Final reports require extensive reconstruction.
- 06
Project knowledge disappears between phases and teams.
The problem is not professional capability. It is a project infrastructure that separates evidence from the people and decisions that give it meaning.
The connected environmental workspace
One evidence chain. Every environmental workflow.
Knoy’s organising idea is simple: evidence should remain connected from the first requirement to the decisions, commitments and reports that follow.
01 / REQUIREMENTR-042
Assess seasonal water-quality effects
02 / SOURCEHYD-03 · p.47
Baseline surface-water monitoring
03 / FINDINGF-WAT-12
Low-flow condition requires mitigation
04 / REVIEWRV-18
Accepted with monitoring note
05 / REPORT§ 8.4
Surface water assessment
06 / COMMITMENTC-027
Quarterly downstream sampling
See the evidence behind the conclusion. The source page, review state and downstream use travel with the finding.
- 01Approval requirements and obligations
- 02Technical studies and field evidence
- 03Agency and stakeholder correspondence
- 04Issues, assumptions and decisions
- 05Specialist and managerial review
- 06Mitigation measures and commitments
- 07Draft and final reporting
- 08Change and version history
How work moves
From project context to a source trail that lasts.
Six connected stages, with evidence and responsibility carried forward.
- 01
Bring the project context together
Requirements, studies, correspondence and prior decisions enter one project boundary.
- 02
Map requirements to evidence
Each obligation is connected to the material that interprets or satisfies it.
- 03
Identify gaps and affected work
Missing support, conflicting findings and downstream impacts become visible.
- 04
Coordinate specialist review
Named reviewers see the source context, decision needed and approval state.
- 05
Carry approved evidence into reporting
Accepted findings move forward with citations and conditions attached.
- 06
Preserve the reasoning and source trail
The project retains why a conclusion was reached—not just the final paragraph.
Change impact
When the project changes, see what changes with it.
Environmental work is rarely linear. New design information, regulator feedback, survey findings and scope changes can alter several disciplines and deliverables at once. The team should not have to reconstruct those consequences manually.
NEW / CORRESPONDENCEAgency letter 14
North Coast Planning Office · fictional
Received 26 Aug · design drainage update requestedPotentially affected workProfessional review required
Requirements3R-018 · R-042 · R-077
Assessments2Surface water · Biodiversity
Open issues4Owners notified for review
Report sections2§ 7.2 · § 8.4
Professional accountability
Connected by technology. Accountable to people.
Knoy is not intended to replace environmental consultants or make final planning, legal, cultural heritage, ecological or regulatory decisions.
The system is intended to:
- Surface relevant project material.
- Preserve citations and source context.
- Highlight gaps and potential impacts.
- Coordinate review and keep approval gates visible.
Privacy as a product principle
Private project files demand more than a privacy promise.
Consultancy files are not generic AI inputs. They can carry commercial, personal, cultural and regulatory sensitivity. Knoy is being designed around explicit project boundaries, controlled access, visible AI data flows and human-controlled outputs.
Client-confidential materialCommercial assumptionsDraft assessmentsPersonal informationCultural heritage informationUnpublished field dataRegulator correspondenceLegal or procurement material
WATTLE CREEK / CONTROL VIEWWorkspace boundary
Project-specific accessNamed rolesOwner · Editor · ReviewerImplemented
Database access policiesProject membership checked at the data layerImplemented
Model route disclosureProvider, region and retention shown before processingDesign direction
Minimum context previewSee the excerpts prepared for a taskDesign direction
Retention and deletion controlsCustomer-visible schedules and deletion stateDesign direction
Private project boundaries
The application has project membership roles and database row-level access policies. Hosting and tenant arrangements still need to be confirmed for each deployment.
Visible AI processing
AI work can use configurable gateway, OpenAI or Anthropic routes. Provider, processing region and retention depend on the selected deployment route and should be made visible before sensitive use.
Minimum necessary context
Structured AI requests cap the number and length of evidence excerpts supplied. More granular, user-visible task controls are still being developed.
Human-controlled outputs
AI-assisted text remains draft material. Citations, obligations and outputs require professional interpretation, verification and approval.
Retention and deletion
Project deletion is supported. Account-level retention schedules, backup handling and customer self-service controls are not yet represented as a complete public commitment.
Auditable activity
The codebase records project audit events and source anchors. It should not yet be described as a complete, customer-facing audit log or export history.
Data ownership
Ownership, licence and processor terms must be set out in agreed legal documents. Knoy’s current public policies remain working drafts.
Impact
Less reconstruction. More time for environmental judgment.
- Less duplicated interpretation
- Faster evidence retrieval
- Earlier visibility of gaps
- Clearer interdisciplinary coordination
- More consistent review
- Stronger continuity into delivery and compliance
Connected evidence layerApprovals
Trace every consent requirement to its evidence, interpretation and approval state.
WF-01128 requirements · 19 need evidence
One connected workspace can preserve a useful source trail beyond a single report—supporting approvals, delivery and compliance without starting from zero at every phase.
The future of connected environmental work
The environment is interconnected. The work that protects it should be too.
Knoy is building the shared evidence layer for environmental projects—from the first requirement to the decisions, commitments and reports that follow.
Talk to Knoy