What the perimeter does today
Automated agents that identify as AI trainers, extractors, or raw tooling are refused at the edge. Friendly SEO crawlers pass. Events are counted in the open pulse so you can see the pressure on the surface for yourself.
- AI agents seen / blocked. bulk training and extraction user-agents (answer engines allowed for product discovery)
- Probes blocked. honeypot paths and bare tool signatures
- Rate limits. noisy pulse and lead abuse is throttled
-
Robots policy. training scrapers disallowed; answer engines + Google/Bing allowed in
robots.txt; assistants map at/llms.txt
No perimeter is perfect. sophisticated scrapers can still disguise themselves. That is why the product keeps your intelligence on your own hardware, rather than on a public web page.
Hardware security. what we are building
S◉LOCK is a private AI operating system. The long game is security that lives with the machine:
- Local by default. models and work stay on hardware you control
- No automatic cloud fallback. intelligence does not quietly leave the desk
- Package integrity. curated installs, measured hardware floors
- Helmsman residency. frontier open weights under your policy
- Enterprise path. multi-seat policy and commercial terms for organisations
Site perimeter is the front door camera. The house is the OS. Founding seats fund both.
Roadmap (honest stages)
- Now. edge AI/probe filter, open counters, robots policy, honeypot
- Next. richer agent fingerprinting, package-level interest signals, audit trail exports for Founding
- On metal. workstation security posture, private network defaults, Helmsman control surface
LOCK