Route cards
Public route cards, evidence packet cards, archive cards, and memory/documentation cards now receive clearer spacing and stronger visual roles.
Route Card Readability
Route Card Readability and Evidence Typography
A static UX/readability pass for route cards, evidence-heavy pages, typography density, long-link wrapping, code/token wrapping, and mobile table overflow while preserving static/read-only boundaries.
v6.6.0 static UX readability pass
Route cards and evidence pages are easier to scan without changing the static safety model.
This pass tightens route-card visual consistency, evidence-heavy page typography, long-link wrapping, code/token wrapping, table overflow handling, and mobile card rhythm across public discovery, reviewer evidence, and memory documentation surfaces.
Evidence typography
Long technical lists get more readable headings, summary cards, line length controls, and less cramped paragraph rhythm.
Mobile resilience
Long URLs, code-like tokens, and wide tables wrap or scroll safely on phone and tablet widths.
Checked route groups
/route-index/, /topic-index/, /sitemap/, /evidence-packets/, /teleodynamic-ecosystem/, /content-architecture/, /semantic-pipeline/, /low-capability-agent-guidance/, /homepage-trust-flow/, and /file-memory-sweep/.
Wrapping rules
Long-link wrapping CSS, code/token wrapping CSS, and table overflow handling protect reviewer-heavy pages from horizontal overflow.
overflow-wrap:anywhere; word-break:break-word; max-width:100%;
Memory preserved
The file memory sweep route, docs/memory index, uploaded UAIX reports, and .uai exports remain intact and discoverable.
Hard boundaries
No runtime AI behavior, no endpoint execution, no live crawling, no remote-site writes, no writable GET actions on Neurokinetic.com, no state mutation through query-string URLs, and no command-and-control claim.
Reviewer-heavy pages now start with summary before depth.
Evidence routes still retain precise public-safe language and manual-review boundaries, but their cards, lists, and tables are tuned for faster scanning before detailed review.
| Area | Readability treatment | Boundary |
|---|---|---|
| Long URLs | Wrap safely inside cards and evidence tables. | No live crawling. |
| Code tokens | Break long token-like strings without layout overflow. | No endpoint execution. |
| Tables | Use responsive overflow regions on narrow screens. | No automated screenshots. |