This is our maintained foundation for explaining AI security and governance. It sets the stage for awareness and education, supports further exploration and development, and provides a basis for future ePlus AI Ignite and AI Security & Governance GTM material. This records the owner's intended direction; it does not represent ePlus adoption or endorsement.
Begin with the shared story to learn the concepts. Use this page to understand how the project is governed and maintained. The repository and public URL retain their existing names.
How the pieces connect
The intent defines the outcome and value. The roadmap organizes the areas of future work. The backlog records specific work, while status summarizes where it stands. Decisions explain why direction or meaning changed. The source map connects that work to the canonical text and its published formats.
| Record | Question it answers | Maintained source |
|---|---|---|
| Intent | What are we trying to achieve, for whom, and within what boundaries? | AISG-INTENT-001 |
| Purpose | Why does this project exist? | Purpose |
| Roadmap | Which areas of development support the intended outcomes? | Roadmap |
| Backlog | What specific work is complete, active or proposed, and what evidence would finish it? | Backlog |
| Status | What is current, what remains uncertain, and what comes next? | Status |
| Decisions | What did the owner decide, why, and what could change it? | Decision log |
| Changes and lessons | What changed in the package, and what should future work learn from it? | Change history and lessons |
| Canonical content and formats | Where do the definitions, architecture details and published artifacts come from? | Source map |
| Authoring | How do humans and agents preserve language, meaning and visual consistency? | Authoring standard and project instructions |
| Reviews and evidence | What was checked, and which design questions remain open? | Review status and release validation |
| Evolution | How do new questions develop without silently replacing the canon? | Exploration guidance |
| Downstream use | How can other material use this foundation and return learning? | Use contract and adaptation register |
The links open public material without requiring a GitHub account. This page is a navigation aid; the linked record owns its information. It does not maintain a second status list or roadmap.
Canonical source and publication formats
The Markdown in content/ holds the shared narrative and architecture meaning. Each PNG depicts its documented visual contract. Detailed guides explain the elements, decisions, interfaces and limits. The presentation teaches a sequence; the website provides access to the text and downloads. Changes to meaning start in the canonical source and then flow to affected formats.
Canonical status means that this is the source maintained for the package. The current architecture content remains a review draft, with substantive findings still open. Source authority, review coverage, publication and approval for a particular use are separate questions.
Foundation for future ePlus work
An AI Ignite or GTM adaptation can reuse the shared definitions, teaching story, examples and architectural rationale while changing depth or context for its readers. It should identify the source revision used and explain its additions. Audience-specific positioning, offer claims, commercial terms and delivery commitments need their own evidence and authority in the receiving context.
The reverse relationship matters too. A reader question, tested scenario or lesson from an adaptation can become a proposal to improve this package. Record the evidence, review the change and update the source deliberately. The roadmap and backlog make that work visible.
Continuing the work
For an orientation, read the shared story and follow its supplier-payment example. For architectural detail, use the guides. For maintenance or a new contribution, read the intent, decisions and status before selecting a backlog item. For a downstream adaptation, start with the use contract and an identified receiving owner.
Feedback is welcome by email; no account is required. Name the section or diagram element and explain what is unclear, missing or incorrect.