Security and demo notice
This site is a demo. It holds no real contracts, drawings or personal information. Defence supply chains do, so in production Shieldworks runs behind the security layer below. 4 of 10 controls are already enforced in this demo; the rest are planned and not active here.
- Northgate Land Systems is a fictional defence company.
- The shops that get work are synthetic. Real shops from public data are labelled and never sent work.
- ITB rules are simplified. Contracts, paperwork and signatures are demo only: nothing is signed or sent.
Security layers
- No drawings or technical dataEnforced now
In this demo: Matching uses part metadata only (process, material, size). Nothing asks for or stores drawings.
In production: Same rule. Drawings move only through the defence company's own secure channel, and only after Shieldworks is registered in the Controlled Goods Program.
- Controlled jobs go to cleared shops onlyEnforced now
In this demo: A controlled job can only be matched to a shop registered in the Controlled Goods Program. The engine enforces it and tests it.
In production: Same rule, plus CPCSC checks and registration expiry alerts before any offer goes out.
- No personal informationEnforced now
In this demo: No names anywhere. Trainees are seat numbers ("Seat 3 of 4") and contacts are role emails.
In production: Keep only what a contract needs, with consent. Shops can export or delete their profile.
- AI suggests, rules decideEnforced now
In this demo: AI only reads part descriptions into fixed labels, checked against a strict format. Answers are saved, so the same parts list gives the same result every time; keyword rules take over if the AI is down. Every match, security check and credit number is plain code, with its reasons shown.
In production: Same design. Every AI answer is logged next to the rule decision it fed, so a person can review or override it.
- Private AIPlanned · not active in demo
In this demo: Part descriptions from the fictional parts list only.
In production: The model runs in a Canadian region with no data retention and no training on customer data. It never sees drawings or controlled technical data.
- Sign-in with two-factorPlanned · not active in demo
In this demo: Demo accounts, one tap, no password.
In production: Company single sign-on plus two-factor authentication for every user. Sessions expire.
- Each company sees only its own dataPlanned · not active in demo
In this demo: Anyone on this network can open any view.
In production: Separate accounts per company with role-based access: a shop sees only its offers, a defence company only its programs, a college only its seats.
- Encrypted everywherePlanned · not active in demo
In this demo: Runs on this laptop over local Wi-Fi.
In production: TLS 1.3 in transit, AES-256 at rest, keys held in a managed key vault and rotated.
- Hosted in CanadaPlanned · not active in demo
In this demo: This laptop.
In production: A Canadian cloud region with a provider that is registered in the Controlled Goods Program. Data stays in Canada. Backups are encrypted.
- Audit trailPlanned · not active in demo
In this demo: A simple log of demo actions (accepts, declines, funding).
In production: Every view, change and export recorded in a tamper-evident audit log that the defence company can hand to the government.
Shieldworks will register with the Controlled Goods Program before it handles any technical data. Until then it never stores drawings. Production controls are a plan, not a certification.