Skip to content

docs: rewrite ninobyte-docs for umbrella scope#1

Open
iamnortey wants to merge 1 commit into
mainfrom
docs/umbrella-scope-rewrite
Open

docs: rewrite ninobyte-docs for umbrella scope#1
iamnortey wants to merge 1 commit into
mainfrom
docs/umbrella-scope-rewrite

Conversation

@iamnortey

Copy link
Copy Markdown
Owner

Summary

Rewrites the Ninobyte case study to reflect what Ninobyte actually is today. The previous README framed it as "Enterprise tooling for Claude agent ecosystems" with three product rows — a 3+ month stale picture that omitted the AWS-native training labs and applied AI infrastructure work.

What changed

  • Umbrella positioning. Ninobyte now framed as three connected product lines: agent tooling, AWS-native training labs, applied AI infrastructure.
  • Product line tables. Each line gets a dedicated table with audience, status, and links to public overview repos where they exist.
  • Mermaid ecosystem diagram showing how the three product lines map to repositories and organizations.
  • Standardized "What's public vs private" section replacing the ad-hoc "Access" section (per editorial standard §5.1).
  • Cross-links to both Ninobyte orgs (now externally verifiable since both org profiles are public).

What is preserved

  • Validation-first, evidence-based, governance-first voice (the strongest part of the original).
  • All cross-links to portfolio and case study.
  • Original badges and structural conventions.

Test plan

  • Tables and Mermaid diagram render on GitHub (preview will confirm)
  • All org and repo links resolve (cross-checked against the now-public org pages)
  • No claim drift — "validated against official Anthropic documentation" preserved
  • No AWS partnership / official certification claims introduced
  • No AI-attribution trailers in commit message

The previous README described Ninobyte as "Enterprise tooling for Claude agent ecosystems" with three product rows. That picture is 3+ months stale and omits the AWS-native training labs (ninobyte-cloudops-lab org) and applied AI infrastructure (ninobyte-labs org) work that now sits under the same brand.

This rewrite:

- Positions Ninobyte as a multi-product effort spanning three connected product lines (agent tooling, AWS-native training labs, applied AI infrastructure).
- Adds product-line tables explaining what lives in each, with status and where to find the public overview.
- Adds a Mermaid ecosystem diagram showing how the three product lines map to repositories and orgs.
- Replaces the ad-hoc "Access" section with the standardized "What's public vs private" template.
- Preserves the validation-first, evidence-based, governance-first voice that was the strongest part of the original.
- Keeps cross-links to portfolio and case study; adds cross-links to both Ninobyte orgs.

Both Ninobyte orgs (ninobyte-cloudops-lab and ninobyte-labs) are now public-profile, which makes the umbrella narrative externally verifiable.
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.

1 participant