Skip to content

#250 child: Standardise Atlas subject taxonomy across Docker and host-runtime providers #262

Description

@Joncallim

Parent: #250. Infra-standardisation review finding; blocked by #259.

Freeze a provider-neutral presentation taxonomy so Docker containers, systemd services, PM2 apps, tmux sessions, processes, listeners, networks and storage can coexist without every provider inventing a different visual grammar.

The taxonomy must preserve provider truth rather than flatten unlike things into a fake common service. Define which runtime node kinds are primary subjects, secondary/context-only subjects, membership/attachment objects, or inspector-only evidence in each lens. Map every supported kind exhaustively and fail closed for unknown future kinds.

Do not use runtime layer/provider labels as causal architecture. Do not duplicate backend semantics or add provider collection scope. The output is a deterministic presentation taxonomy with shared identity/state/freshness/ambiguity rules and explicit exceptions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions