How This Library Is Intended to Be Read
These documents are not meant to be read sequentially.
Boundary Notice
Docs · How This System Is Actually Exposed
This page does not publish patent documents.
STELAFOX does not disclose patent specifications, internal algorithms,
or implementation-level designs in document form.
What we publish is how the system is experienced, tested, and activated —
not how it is reverse-engineered.
1. What Is Publicly Accessible
We expose our core technologies through capsules and operational tools,
not through PDF patents or whitepapers.
Public access includes:
-
Core Capsules (GXC format)
Activated via LLMs (ChatGPT / Gemini / Claude)
Available through the Core page on this site -
Operational Bridge Tools
-
Photo / Video Viewer
-
Easy / Pro / Cinema
-
JVP / JVM
-
BUIL
-
These tools are not demos.
They are live bridges connecting current AI systems to upcoming hardware and vision systems.
2. What a Capsule Is (And What It Is Not)
A capsule is not a document.
A capsule is an executable knowledge boundary.
When uploaded to an LLM:
-
It activates a constrained operating context
-
It enforces structural rules and logic boundaries
-
It allows questioning, probing, and construction without exposing source logic
Capsules are:
-
Time-limited
-
Scope-limited
-
Purpose-defined
This is intentional.
3. Core vs Detail vs Sub — How the System Is Structured
Our intellectual property is layered by exposure level, not by importance.
Core (4 systems)
-
GLOS (Grid Logic OS)
-
LCTS
-
SLM AGI OS
-
Vision OS
These are:
-
Exposed only via capsules
-
Executed through Cloud Run
-
Interacted with through LLM activation
Detail / Sub layers
-
Validated through GPT / Gemini test cycles (T5)
-
Currently in MVP validation (T6–T7)
-
Not distributed as documents
-
Not published as specifications
4. Why You See Tools Instead of Patents
You are not supposed to "read" this system.
You are supposed to use it.
The following are intentional bridge layers:
-
Photo / Video Viewer
-
Easy / Pro / Cinema
-
JVP / JVM
-
BUIL
These tools exist because:
-
Vision will arrive before explanation
-
Spatial logic must be felt before it is understood
-
Hardware (single-lens + z_Logic) arrives in 2026 H1
-
These tools are the evidence that the transition has already started
5. Timeline (Publicly Verifiable)
-
Capsules distributed: Already live
-
Debugging OS exposed to researchers: Already used
-
LCTS-based spatial reasoning: Already tested
-
Vision OS synthesis: In progress
-
Single-lens + z_Logic product: 2026 H1
Nothing here is hypothetical.
6. Why We Do Not Publish Patent PDFs
Patent documents are:
-
Legal artifacts
-
Not operational interfaces
-
Not how systems are validated
-
Not how AI actually learns or behaves
Publishing them would:
-
Mislead non-experts
-
Invite shallow interpretation
-
Break the boundary between use and replication
We deliberately refuse that model.
7. If You Want to Go Deeper
There are only three valid ways in:
-
Activate a capsule
-
Operate a bridge tool
-
Engage through controlled collaboration
Everything else is noise.
Final Note
This page exists to clarify where the system is visible
and where it is intentionally not.
STELAFOX is not a documentation company.
It is a system-transition company.
☑️ Docs
Choose how deep you go.
This documentation is not organized by topic.
It is organized by role, intent, and responsibility.
Beginner
Start without understanding everything
This section is for people who want to use, not analyze.
You do not need to know:
AI theory
Vision systems
Spatial logic
Internal architecture
You only need to know:
What problem you are solving
What tool to open
What output you want
You will find here:
How to run Photo / Video Viewer
Easy / Pro / Cinema usage
What JVP / JVM are meant for
What BUIL is for (and what it is not)
You will NOT find here:
Algorithms
Model explanations
System internals
If you are asking "why does this work?"
You are already past this level.
Operator
Use the system intentionally
This section is for people who operate the system as part of work.
You are:
Designers
Engineers
Producers
Researchers using AI as a tool
Teams deploying capsules internally
You will find here:
Capsule activation rules
Debugging OS usage
Operational constraints
Tool chaining (Viewer → BUIL → Capsule)
Failure cases and recovery patterns
You are expected to:
Follow structure
Respect system boundaries
Understand cause–effect at the tool level
This is where results become reproducible.
Researcher
Read the system as a structure, not a product
This section is intentionally difficult.
It is for:
PhD-level researchers
AI lab members
Vision / robotics / cognition researchers
Advanced partners under evaluation
You will find here:
Structural descriptions (not implementations)
Logical boundaries (GLOS / LCTS / SLM AGI)
Why the system is built this way
What is deliberately excluded
What cannot be simulated by LLM-only systems
You will NOT find here:
Patent documents
Source code
Training data
Reproducible blueprints
If you are comfortable here,
you already understand why those things are missing.
Partner
If you are here, you already know why
This section is not open by default.
It is for:
Strategic partners
Institutional collaborators
Hardware / optics / robotics manufacturers
Defense / medical / industrial entities
Access is granted by:
Collaboration
Contract
Joint validation
Or direct invitation
What exists here is not documentation.
It is coordination.
A note on patents and disclosure
STELAFOX does not use documentation as disclosure.
Patents exist as:
Legal protection
Boundary definition
Timestamped claims
Public interaction happens through:
Capsules
Tools
Operational systems
This is deliberate.
How to choose where you belong
If you want to:
Try something → Beginner
Run something → Operator
Understand structure → Researcher
Build together → Partner
If none of these fit,
this system may not be for you — yet.
Closing line (recommended)
This Docs section is not meant to explain everything.
It is meant to prevent misunderstanding.