Philosophy to orientation
The philosophical blueprint gives the high-level boundary. Start Here translates the same ideas into introductory language for new readers.
Static concept map
A static, non-executing map that connects the philosophical blueprint to the core research routes, claim boundaries, review gates, and public evaluation packets.
This is a map, not a machine. It organizes the public Teleodynamic AI research story into connected routes and review states. It does not implement self-maintaining intelligence, constraint closure, active inference, glyph interpretation, model training, live telemetry, or autonomous behavior.
The purpose is to keep the philosophical blueprint, introductory pages, research foundations, roadmap, glyph layers, evaluation lab, and public packet templates aligned without widening claims beyond available evidence.
The map below shows the intended reading and handoff relationships between major routes. Every edge is a static documentation relationship, not a runtime dependency or live agent workflow.
The matrix keeps each major route honest about what it contributes, what it does not prove, and which public evidence path is appropriate.
| Route | Status | What it contributes | What it does not claim | Evidence or next review path |
|---|---|---|---|---|
| Bounding the Bleeding Edge | Philosophical | Frames Teleodynamic AI as a conceptual architecture and implementation handoff path. | Does not claim a living, conscious, autonomous, or deployed self-maintaining AI. | Use this route to orient implementation teams before building elsewhere. |
| Start Here | Philosophical | Introduces resource-bounded learning, no-op, and constraint-maintaining language. | Does not prove resource closure exists in deployed software. | Pair with the roadmap and claim-boundary pages. |
| Research Foundations | Research reference | Explains the homeodynamic, morphodynamic, and teleodynamic hierarchy. | Does not make biological-equivalence claims about current software. | Use source-reference review before any claim widening. |
| Roadmap | Implementation handoff | Organizes future work into phases and evidence boundaries. | Does not say those phases have already been implemented here. | Convert into static packet checklists or external testbed milestones. |
| Glyph Object Specification | Implementation handoff | Defines a layered record model for expression, structure, comparison, and reviewed meaning. | Does not perform glyph interpretation or exact translation on this site. | Use the expression-concept review packet and human review gates. |
| Evaluation Lab | Static artifact | Lists metric families, review gates, audit fields, and dashboard examples. | Does not certify any prototype as safe or teleodynamic. | Use evaluation packets and reviewer walkthroughs. |
| Public Evaluation Packets | Static artifact | Provides non-executing JSON, Markdown, and HTML templates. | Does not execute validation, train models, probe networks, or validate credentials. | Download packets for reviewer use and external implementation planning. |
| Future experimental testbeds | Not implemented here | Would be responsible for resource loops, active models, dashboards, and simulator behavior. | Must not use this site as evidence that those systems already exist. | Requires independent artifacts, logs, screenshots, validation, and third-party review. |
The philosophical blueprint gives the high-level boundary. Start Here translates the same ideas into introductory language for new readers.
Research Foundations explains why pattern formation is not enough. Roadmap turns that distinction into implementation phases and evidence expectations.
Glyph Object Specification defines how meaning must stay layered. Evaluation Lab defines how claims should be checked before public authority widens.
Public Evaluation Packets turn review expectations into static artifacts that can be downloaded, filled out, and reviewed without runtime behavior.
If evidence is missing, the correct public documentation action is to refuse the wider claim, mark the item unresolved, or route it to human review.
Execution, simulation, local sandboxes, semantic interpreters, and dashboards belong in dedicated implementation environments, not this philosophical page.
Deep route polish
Connects the philosophical blueprint to Start Here, Research Foundations, Roadmap, Glyph Object Specification, Evaluation Lab, and Public Evaluation Packets without adding runtime AI behavior.
The concept map provides a reading and evidence relationship between major Teleodynamic.com routes. It keeps philosophical framing, research references, implementation handoffs, and static evidence artifacts distinct so public claims do not widen simply because pages are connected.
A reader can start at the philosophical blueprint, move to Research Foundations for the homeodynamic/morphodynamic/teleodynamic hierarchy, consult the Roadmap for future implementation phases, and use Public Evaluation Packets for static review templates.
| Focus | What to inspect |
|---|---|
| Philosophical route | |
| Claim matrix | |
| Evidence packet |
The route is static local documentation. It does not validate implementation, run telemetry, or certify safety. Unsupported implementation claims should remain no-op or human-review items.