Knowledge OS — LTRing · TEvEP · RUT · argument map

Part: Engineering · Chapter: Knowledge OS — LTRing · TEvEP · RUT · argument map · Edition: 2026-07-15
Keywords: knowledge OS, LTRing, TEvEP, RUT, argument map, IEML, Path, Frame, Package, ACL
Glossary: LTR, Path, TEvEP, RUT, USL, IEML — see GLOSSARY

At a glance

• A knowledge operating system stacks proposition structure (LTRing), method (TEvEP), operational boards (RUT), and editable scenario graphs (argument map).
• IEML supplies computable roles / metalanguage; MD/git supplies audit trails.
• Access pattern: trusted network free · public OTP only for configured allowlist (no personal identifiers in this chapter).
• Product surfaces live under Situation Monitor public paths; full ZF1 recovery stays lab-only.

Online references (live)

• IEML
• Collective intelligence
• Semantic Web
• Transclusion
• Design pattern
• IEMLdev/ieml (Python parser / dictionary)
• INTLEKT

Offline figures (this chapter)

Offline snapshot omitted in this web edition. Figure 1 — Product surfaces over shared IEML roles, MD/git, and ACL.

Offline snapshot omitted in this web edition. Figure 2 — LTRing hierarchy (Soletrando doctrine).

Index card (the Knowledge Base) — how Situation Monitor’s knowledge products compose: recovered LTRing doctrine + modern Path UI, TEvEP method, RUT operational matrix, argument map with IEML tool words, without publishing personal identities.

---

0. Why a “Knowledge OS”

Engineering work produces more than code: propositions, processes, scenarios, and evidence. A Knowledge OS is a stack that:

1. Structures claims so they can be reused (not only documents).
2. Operates them in time (seven-step cycles, events).
3. Maps possible scenarios with typed relations.
4. Gates who may edit under zero-trust-ish network rules.
5. Tracks changes under versionable text (MD/git), optionally projected into a graph DB.

This chapter freezes the conceptual design discussed in lab recovery and product work (2026-07). Implementation paths and hostnames are redacted or generalized; public product URLs are listed as examples only.

---

1. Layer map

Cross-links in this bible: IEML · WWW Platform · Knowledge management · Information theory.

---

2. LTRing — proposition hierarchy

2.1 Doctrine (from recovered “Soletrando” text)

Everything said or learned can be cast as a proposition. In LTRing:

Engineering slogan: do not reinvent Packages or LTRs—search and symlink first.

2.2 UI language (Global-V4 mockups)

Recovered product design uses a white canvas, charcoal chrome bar, vertical spine, hierarchical cards, and level pills:

view · frame · paragraph · sentence

Offline snapshot omitted in this web edition. Figure 3 — Path reader (Global-V4 view). Original product mockup; no personal data.

Offline snapshot omitted in this web edition. Figure 4 — Stream of Paths and cards (Global-V4 stream).

2.3 Modern implementation note (lab)

A Vue 3 + Vite Path reader + stream was built to match Global-V4 (ltring/web/), served under a lab gate at /tring/app/. Legacy Zend Framework 1 recovery remains reference-only behind the same ACL gate—not the long-term public stack.

Privacy: demo seed content uses historical/scientific public examples (e.g. history of electricity). No real contributor identities are published in this chapter.

---

3. TEvEP — method lens

TEvEP = Tempo · Evento · Espaço · Pessoas.

• Align the team on the same four dimensions before execution.
• Pi (Padrão Inteligente): always 7 tempos; complexity opens another Pi of 7 (fractal 7 / 49 / 343 / …).
• Product surface: block editor with layers such as 7T, 7F, 6M, CESAQ (operational taxonomies).

Related: process-first intelligence thesis (intelligence as organized information in processes, not only individual trait)—see philosophy/systems notes in Knowledge management.

---

4. RUT — operational board

R.U.T. (Rede de Unidades de Trabalho) is the high-performance cycle board:

• Matrix: pilots × times (T1–T7) × events (Ev1–Ev7).
• Status vocabulary: pending · planned · done · blocked (editable board + XLS mirror with formulas).
• Desdobramentos: event titles + subtasks under each pilot/time.

Redaction rule for this bible: pilot labels are abstract (P1…Pn); real personal names from any industrial case file are not reproduced here. Generic case: CICLO 001 · Business Transform · Alta Performance.

Public product example path: Situation Monitor /homosapiens/ (RUT board app).

---

5. Argument map — scenarios + chat-as-edit

5.1 Role

/agents (product) is an argument / scenario map, not free-form Q&A only:

• Nodes: claim · scenario · evidence · opposition · …
• IEML tool words (roles) on nodes: e.g. root, initiator, process, destination, time, location, manner, instrument, cause.
• Relations: supports · opposes · expands · scenario_of · evidence_for · implies · part_of · …
• Chat is an edit request tool → mutates graph → rewrites map.json / MAP.md / appends CHANGELOG.md.

5.2 Doctrine nodes (examples, non-personal)

5.3 Graph projection (lab)

Neo4j is preferred as a query projection of MD/git (not a replacement). GraphQL is optional as an API façade over Neo4j. Lab compose binds localhost only; not part of public SM edge by default.

---

6. IEML parser (engineering truth)

Official open stack is primarily Python (IEMLdev/ieml):

Lab notes live outside the bible in repo docs (docs/IEML-PARSER-NOTES.md) when present. GPL-3.0 applies to the library—integration into proprietary products needs license review.

See full metalanguage card: IEML.

---

7. Access control pattern (no PII)

This chapter does not list phone numbers, names, or credentials. Operators configure allowlists and secrets via environment, never in gitbook prose.

Same pattern is reused across agents gate, LTRing lab gate, and related product apps.

---

8. Privacy & redaction policy (this chapter)

If a figure or quote would re-identify a private person, omit or anonymize.

---

9. Primary literature & references

---

10. See also

• WWW Platform — IEML
• IEML
• Knowledge management
• Information theory
• Engineering index
• Sociotropia & sociomorphing

---

11. One-line summary

Knowledge OS = LTRing structure + TEvEP method + RUT operations + argument-map scenarios + IEML roles + MD/git audit + network ACL—without publishing people.