Silica Lab Stack v1.0
Public framing of the stack and deployment logic. This is the current public reference point.
Docs
Public notes that make the stack easier to trust.
The docs surface is public by design, but still scoped. It explains the operating model without publishing private implementation details.
Allowed / Controlled / Blocked
Plain-language explanation of how the boundary model works in practice.
Home, Academy, School, Builder
Public comparison of the four deployment contexts and the operational differences between them.
Public docs policy
What is deliberately excluded from public docs.
| Excluded | Reason |
|---|---|
| Private credentials or environment details | Operational security matters more than public performance. |
| Raw private datasets or records | Silica Lab does not trade trust for technical theatre. |
| Internal-only topology specifics | Public trust requires clarity, not reckless disclosure. |
Implementation route
If the public notes are enough, that is good. If you need a route-specific conversation, use the protected enquiry form and keep the problem high-level at first contact.
Next step