Skip to content

docs(spec): clarify managed-container boundary - #109

Draft
projectious wants to merge 1 commit into
feat/deployment-credential-hardeningfrom
docs/clarify-managed-container-boundary
Draft

docs(spec): clarify managed-container boundary#109
projectious wants to merge 1 commit into
feat/deployment-credential-hardeningfrom
docs/clarify-managed-container-boundary

Conversation

@projectious

@projectious projectious commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • stack this follow-up on draft PR docs(spec): define agent-native execution and credential hardening #108
  • define the infrastructure/workload boundary by the independently usable capability produced
  • exclude atomic managed-container creation from ainfra when no separable host or cluster results
  • identify Vast.ai-style atomic container capacity as an Aibox adapter candidate

Validation

  • scripts/validate-v1-spec
  • roadmap phases remain sequential
  • git diff --check

Review focus

Please review only the managed-container boundary relative to the agent-native baseline in #108.

@projectious
projectious force-pushed the docs/clarify-managed-container-boundary branch from 8847be4 to dd6cda1 Compare August 24, 2026 14:16
@projectious
projectious changed the base branch from v1.x-dev to feat/deployment-credential-hardening August 24, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants