Public demo — read-only replica of Navo service detail. Edit, add, and delete controls are disabled on this website.
TFE State
datatfeInfrastructure as code
Remote state and run history.
datainfrastructuredemo
Technical Summary
Workspace-per-env with locked applies.
Advantages
- Clear role in the Infrastructure as code zone of the map
- Topology and narrative stay in versioned architecture YAML
- Visible to unlimited viewers without a platform portal seat
Who / What / When / Where / Why
- Who
- Infrastructure as code owners and on-call for TFE State
- What
- Remote state and run history.
- When
- Continuous — part of the always-on architecture map
- Where
- DevOps platform · Infrastructure as code
- Why
- Documents how TFE State connects in the living map so teams share one Git-backed model.
Related Services
Related Repos
tfe-servicedevops-platform
Links
TFE State runbook
wiki/wiki/tfe.md
In-app wiki path (demo stub)
Source repository
repohttps://example.com/repos/tfe
Example repo link for the public demo
Ops dashboard
urlhttps://example.com/dashboards/tfe
Add Service Link
DevIn the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.
Local annotations (overlay)
In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.
Ready to contribute in a real deployment? Architecture maps ship through Git PRs — not browser-only edits. Share & export docs