Institutional layer · STGP
Structured institutional interaction, without contaminating the operational base.
UrbeIA's institutional layer allows building tools for observations, claims, proposals, simulations and audited requests without converting external interaction into system truth.
What the institutional layer is
STGP is UrbeIA's decoupled institutional layer. It does not exist to rewrite the system's urban reading, but to formalise how institutions, teams or authorised actors interact with that reading in a structured and auditable way.
- Institutional observations
- Formal claims
- Non-executive proposals
- Simulations linked to proposals
- Audited requests
- Filtered transparency surfaces
What this layer does not do
- Does not alter the system's operational base
- Does not convert external opinion into urban truth
- Does not embed strong political deliberation in the base infrastructure
- Does not mix participation and operational state without boundary
- Does not turn the core into a forum, chaotic file or institutional pressure layer
The separation is deliberate. Institutional interaction exists, but does not contaminate the layer that sustains urban reading.
What tools it allows building
Institutional observations
Formal channels to register structured observations about specific situations, zones or states.
Claims and proposals
Tools to formulate audited proposals or claims without automatically altering the system base.
Simulation linked to proposal
Layers where an institutional proposal can connect to simulation, contrast or prior analysis before any decision.
Audited requests
Circuits where an institution or authorised actor opens a formal request with traceability, context and follow-up.
Filtered transparency
Surfaces that expose part of the urban reading or institutional interaction without fully opening the system.
Why this separation matters
In institutional product, the problem is not just having data or dashboards. It is being able to structure formal interaction without the base infrastructure losing stability, clarity or auditability.
STGP resolves that tension: opens useful institutional software, without mixing opinion with state, without collapsing the operational layer, and without turning the system base into a space of structural confusion.
The separation is not a limitation. It is what makes this layer viable in serious environments.
Not everything institutional needs to enter the base to be useful.
STGP exists precisely to resolve that: open formal, auditable and structured interaction without turning the operational infrastructure into a space of noise, opinion or mixed responsibilities.