Before external use
Two lists that travel with the portfolio. The first is every claim that still needs an evidence gate before it is spoken loosely. The second is material that was deliberately kept out of the portfolio and belongs in an NDA room.
View only · files are not offered for download
Slide 20 — IP & Defensibility
Risk. The count can be read as a patent portfolio if the qualifier is dropped in conversation.
Required. Internal invention-theme register, counsel review, and a decision on which themes remain candidates vs. trade secret.
Slide 12 — Sensor Innovation
Risk. Readers may infer a manufactured, certified product.
Required. Engineering specification pack, BOM hypothesis, lab protocol. Do not present samples as products until they exist.
Slide 10
Risk. May be heard as already instrumented across those environments.
Required. Pilot designs, capture-quality benchmarks, and a written policy that schools stay camera-first.
Slide 11
Risk. May be heard as production-grade models already trained and promoted.
Required. Benchmark plan, calibration protocol, field-validation gates before any production promotion.
Slide 14
Risk. Implies integrations with ticketing vendors that are not contracted.
Required. Named integration targets under NDA; no public vendor claims until agreements exist.
Slide 15
Risk. May be heard as a live consumer product.
Required. Prototype evidence and a destination pilot design.
Slides 17–18
Risk. A designed map can be mistaken for current revenue.
Required. Keep language as designed architecture. Introduce figures only from a financial model under NDA.
Slide 16
Risk. May be modelled as near-term security ARR.
Required. Keep Phase 4 gated. Do not put it in a base-case revenue build.
Slide 23
Risk. Can be misread as official government alignment or endorsement.
Required. Use only the qualified language in the portfolio. No ministry, federation or 2034 marks without evidence.
Slides 8–9
Risk. Implies institutional write-access and data-sharing that does not yet exist.
Required. Data-governance design, consent model, and pilot institutions before any public continuity claim.
Slide 05
Risk. May be heard as an existing API product.
Required. Service catalogue remains target architecture until a versioned interface exists.
Slide 17
Risk. Implies a live audience and an ads stack.
Required. Do not present media-kit numbers until there is a real feed and a real audience.
Public disclosure can destroy novelty. Candidates are mentioned; charts are not.
Core know-how. Belongs in a technical diligence room, not a travelling portfolio.
Trade secret. The portfolio shows the sensing philosophy, not the method.
Until evidenced, names create implied endorsement and relationship risk.
Lives with the pitch and the data room, not in this architecture portfolio.
Useful in diligence; harmful if published ahead of a control environment.
Sensitive by nature. Summarise the principle; share the policy under NDA.
Likeness and privacy. No operational evidence is faked or pasted into this deck.
Commercial sensitivity. Architecture is shown; suppliers are not.
Overwhelms the reader and leaks roadmap. Selected families are enough.