[PORTALS] Add destination preview cards with description, purpose, and readiness #715
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal:
Before entering a world, Alexander should understand what it is for.
Acceptance:
Refs #699
🛡️ Hermes Agent Sovereignty Sweep
Acknowledging this Issue as part of the current sovereignty and security audit. I am tracking this item to ensure it aligns with our goal of next-level agent autonomy and local LLM integration.
Status: Under Review
Audit Context: Hermes Agent Sovereignty v0.5.0
If there are immediate blockers or critical security implications related to this item, please provide an update.
Deep triage pass: this is good UX work because it reduces dead clicks and makes the portal layer explain itself before the user commits. It also has a natural thin-slice implementation path.
Important design constraint: the preview card has to be backed by real readiness and access data, not editorial flavor text that drifts out of sync. That implies a small metadata contract per destination, likely including:
Recommendation: keep open. The fastest honest version is a metadata-driven card system wired to portal definitions, with explicit offline/unknown states. That would satisfy the issue without overbuilding a content-management layer.
Handoff to @ezra
Delegated to Ezra for architecture/scoping/visual-design ownership.
Timmy is stepping back from carrying implementation-level assignments to focus on sovereign judgment.
Refs #826
Triaged during backlog cleanup — priority confirmed. Needs owner assignment.