-
Notifications
You must be signed in to change notification settings - Fork 4
Add Studio Information Architecture (v3.8) #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
maxvydrin
wants to merge
1
commit into
constructorfabric:main
Choose a base branch
from
maxvydrin:add-studio-ia
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,255 @@ | ||
| # Studio Information Architecture — v3.8 | ||
|
|
||
| Mind-map export. Root / central node: **Organization**. | ||
|
|
||
| > Cross-cutting layers (aspects, not containers): Collaboration · Governance-enforcement · Customization. These surface across the whole map — they are not places/nodes. | ||
|
|
||
| ``` | ||
| Organization | ||
| ├─ Workspace | ||
| │ ├─ Project | ||
| │ │ ├─ Executive summary | ||
| │ │ ├─ Dashboards | ||
| │ │ ├─ Project Graph | ||
| │ │ │ ├─ Object Browser | ||
| │ │ │ │ └─ ⓘ Filter & inspect by type · status · owner · staleness — a filter over the graph, not a catalog; it doesn't duplicate it. Docs → Documents; Work Artifacts → Workflow runs. | ||
| │ │ │ ├─ Object detail | ||
| │ │ │ │ ├─ Attributes | ||
| │ │ │ │ ├─ History | ||
| │ │ │ │ ├─ Evidence | ||
| │ │ │ │ └─ Related objects | ||
| │ │ │ └─ Graph views | ||
| │ │ │ ├─ Dependencies and traceability | ||
| │ │ │ ├─ Staleness and risk view | ||
| │ │ │ └─ Timeline changes / History | ||
| │ │ ├─ Lifecycle Model | ||
| │ │ │ ├─ Actor | ||
| │ │ │ │ ├─ Humans | ||
| │ │ │ │ ├─ AI agents | ||
| │ │ │ │ ├─ External tools | ||
| │ │ │ │ ├─ External systems | ||
| │ │ │ │ └─ Automated pipelines | ||
| │ │ │ ├─ Stages | ||
| │ │ │ │ ├─ Plan | ||
| │ │ │ │ │ ├─ Intent | ||
| │ │ │ │ │ ├─ Vision | ||
| │ │ │ │ │ ├─ Discovery | ||
| │ │ │ │ │ ├─ Strategy | ||
| │ │ │ │ │ └─ Definition | ||
| │ │ │ │ ├─ Build | ||
| │ │ │ │ │ ├─ Design | ||
| │ │ │ │ │ ├─ Construction | ||
| │ │ │ │ │ ├─ Validation | ||
| │ │ │ │ │ └─ Release | ||
| │ │ │ │ └─ Operate | ||
| │ │ │ │ ├─ Operation | ||
| │ │ │ │ ├─ Support | ||
| │ │ │ │ ├─ Intelligence | ||
| │ │ │ │ ├─ Optimization | ||
| │ │ │ │ └─ Evolution | ||
| │ │ │ ├─ Activities | ||
| │ │ │ ├─ Input | ||
| │ │ │ ├─ Output | ||
| │ │ │ ├─ Quality gates | ||
| │ │ │ └─ Synchronisation checkpoints | ||
| │ │ ├─ Workflows | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Workflows per workspace, not per project |
||
| │ │ │ ├─ Flow Catalog | ||
| │ │ │ ├─ Visual workflow builder | ||
| │ │ │ ├─ Runs and history | ||
| │ │ │ ├─ Produced artifacts | ||
| │ │ │ │ ├─ Work Artifacts → PR · Test · Build · Release · Deployment (latest + gate status) | ||
| │ │ │ │ └─ Document Artifacts → land in ▸ Documents (e.g. PRD · register · report · release notes) | ||
| │ │ │ ├─ Approvals / exceptions / handoffs | ||
| │ │ │ └─ Validators and Policies | ||
| │ │ ├─ Recommendations & Actions | ||
| │ │ │ ├─ Detected gaps & risks | ||
| │ │ │ ├─ Recommendations / Next actions | ||
| │ │ │ ├─ Prepared actions | ||
| │ │ │ ├─ Action approval queue | ||
| │ │ │ ├─ Write-back | ||
| │ │ │ └─ Trust level | ||
| │ │ ├─ Documents | ||
| │ │ │ ├─ Competitive Intelligence | ||
| │ │ │ │ ├─ Competitive register | ||
| │ │ │ │ ├─ Comparison matrix | ||
| │ │ │ │ └─ Pricing benchmark | ||
| │ │ │ ├─ Strategy & Planning | ||
| │ │ │ │ ├─ Product strategy brief | ||
| │ │ │ │ ├─ Roadmap (Now / Next / Later) | ||
| │ │ │ │ ├─ One-pager / narrative | ||
| │ │ │ │ └─ Opportunity statement | ||
| │ │ │ ├─ Specs & Requirements | ||
| │ │ │ │ ├─ Problem statement | ||
| │ │ │ │ ├─ BRD | ||
| │ │ │ │ ├─ PRD | ||
| │ │ │ │ ├─ Feature spec | ||
| │ │ │ │ └─ Requirement | ||
| │ │ │ ├─ Metrics & Performance | ||
| │ │ │ │ ├─ Scorecard | ||
| │ │ │ │ └─ EPSVS scorecard | ||
| │ │ │ ├─ Launch & Release | ||
| │ │ │ │ ├─ Launch plan / GTM checklist | ||
| │ │ │ │ └─ Release notes | ||
| │ │ │ └─ Engineering & Ops | ||
| │ │ │ ├─ Design | ||
| │ │ │ ├─ ADR | ||
| │ │ │ ├─ Decision | ||
| │ │ │ ├─ Decomposition | ||
| │ │ │ ├─ Test plan / Validation report | ||
| │ │ │ ├─ Runbook | ||
| │ │ │ └─ Postmortem | ||
| │ │ ├─ Developer tools | ||
| │ │ │ ├─ CLI | ||
| │ │ │ ├─ IDE plugins | ||
| │ │ │ ├─ MCP servers | ||
| │ │ │ └─ Notifications / alerts | ||
| │ │ ├─ Quality Gates (applied) | ||
| │ │ │ ├─ Applied gates | ||
| │ │ │ └─ Gate status | ||
| │ │ └─ Access & Roles (project scope) | ||
| │ ├─ Teams and Roles | ||
| │ │ ├─ Teams | ||
| │ │ ├─ Role assignments (workspace scope · grants from Org catalog) | ||
| │ │ └─ Members & seat approvals | ||
| │ ├─ Shared assets | ||
| │ │ ├─ Guidelines | ||
| │ │ ├─ Templates | ||
| │ │ ├─ Processes | ||
| │ │ ├─ Workflow blueprints | ||
| │ │ └─ Shared artifacts | ||
| │ ├─ Settings | ||
| │ │ ├─ Model routing | ||
| │ │ ├─ Connectors (bound) | ||
| │ │ ├─ Localization | ||
| │ │ ├─ Guardrails & Quality gates | ||
| │ │ └─ Secrets & credentials (scoping · rotation) | ||
| │ ├─ Environments | ||
| │ │ └─ dev · staging · prod (scopes connectors & secrets) | ||
| │ └─ Audit log (workspace scope) | ||
| ├─ Kits & Gears | ||
| │ ├─ Kit (package / anatomy) | ||
| │ │ ├─ Reference architecture | ||
| │ │ ├─ Ontology | ||
| │ │ ├─ Templates and examples | ||
| │ │ ├─ Sample data (seed graph) | ||
| │ │ ├─ Actions and validators | ||
| │ │ ├─ Rules and policies | ||
| │ │ ├─ Kit Workflows | ||
| │ │ ├─ Deployment patterns | ||
| │ │ └─ Gears building blocks | ||
| │ ├─ Function Kits | ||
| │ │ ├─ SDLC Kit (open-source base / default) | ||
| │ │ ├─ Product Management Kit | ||
| │ │ ├─ Architect Kit | ||
| │ │ ├─ Engineering Management Kit | ||
| │ │ ├─ DevOps Kit | ||
| │ │ ├─ QA Kit | ||
| │ │ ├─ Support Kit | ||
| │ │ ├─ HypoFinder Kit (research · domain) | ||
| │ │ ├─ M&A Kit (domain) | ||
| │ │ └─ Any other Kit (placeholder) | ||
| │ ├─ Gears | ||
| │ │ ├─ Identity | ||
| │ │ │ └─ IdP, SSO, tenant identity, user lifecycle | ||
| │ │ ├─ Authorization | ||
| │ │ │ └─ RBAC, ABAC, granular roles, delegated administration | ||
| │ │ ├─ Events | ||
| │ │ │ └─ event bus, schemas, routing, audit events | ||
| │ │ ├─ Serverless | ||
| │ │ │ └─ functions, workflows, safe runtime, connectors | ||
| │ │ ├─ GenAI | ||
| │ │ │ └─ model gateway, routing, prompts, evaluation | ||
| │ │ └─ Platform | ||
| │ │ └─ audit, billing, notifications, APIs, integrations | ||
| │ └─ Customization | ||
| ├─ Integrations | ||
| │ ├─ ⓘ Studio connects per capability, not per vendor — so a multi-product vendor (GitHub, Jira…) appears in several categories by design; the graph spans tools cross-vendor. | ||
| │ ├─ Plan | ||
| │ │ ├─ Product & roadmapping | ||
| │ │ │ └─ Jira Product Discovery · Productboard · Aha! · Linear | ||
| │ │ ├─ Docs & knowledge | ||
| │ │ │ └─ Confluence · Notion · MS Office · Google Workspace | ||
| │ │ ├─ Design & whiteboarding | ||
| │ │ │ └─ Figma · Miro · FigJam | ||
| │ │ ├─ Customer feedback / VoC | ||
| │ │ │ └─ Canny · UserVoice · Productboard Insights · Dovetail | ||
| │ │ ├─ Market & competitive intelligence | ||
| │ │ │ └─ Similarweb · G2 · Crunchbase · Klue · Crayon | ||
| │ │ └─ User research & surveys | ||
| │ │ └─ Dovetail · UserTesting · Maze · Qualtrics | ||
| │ ├─ Build | ||
| │ │ ├─ Source control | ||
| │ │ │ └─ GitHub · GitLab · Bitbucket | ||
| │ │ ├─ IDE & coding agents | ||
| │ │ │ └─ VS Code · JetBrains · Cursor · Claude Code · Windsurf | ||
| │ │ ├─ Issue / work tracking | ||
| │ │ │ └─ Jira Software · Azure DevOps · Linear | ||
| │ │ ├─ CI/CD & build | ||
| │ │ │ └─ Jenkins · GitHub Actions · GitLab CI · Harness | ||
| │ │ ├─ Code quality | ||
| │ │ │ └─ SonarQube · CodeClimate · Codecov | ||
| │ │ ├─ Application security (SAST/DAST/SCA) | ||
| │ │ │ └─ Snyk · Semgrep · Checkmarx · Veracode · OWASP ZAP | ||
| │ │ ├─ Test management & QA automation | ||
| │ │ │ └─ TestRail · Xray · Zephyr · Playwright · Cypress · BrowserStack | ||
| │ │ ├─ API design & specs | ||
| │ │ │ └─ Postman · SwaggerHub / OpenAPI · Stoplight | ||
| │ │ ├─ Package & artifact registries | ||
| │ │ │ └─ Artifactory · Nexus · npm · PyPI | ||
| │ │ └─ Container registries | ||
| │ │ └─ Docker Hub · Amazon ECR · GHCR · Harbor | ||
| │ ├─ Operate | ||
| │ │ ├─ Cloud & infrastructure | ||
| │ │ │ └─ AWS · GCP · Azure · Kubernetes | ||
| │ │ ├─ Observability & monitoring | ||
| │ │ │ └─ Datadog · Grafana · Prometheus · New Relic · OpenTelemetry | ||
| │ │ ├─ Incident & on-call | ||
| │ │ │ └─ PagerDuty · Opsgenie · incident.io | ||
| │ │ ├─ Support & service desk | ||
| │ │ │ └─ Zendesk · Intercom · ServiceNow · Jira Service Mgmt | ||
| │ │ ├─ Product analytics | ||
| │ │ │ └─ Amplitude · Mixpanel · PostHog · Pendo (also Plan: value sizing) | ||
| │ │ ├─ Data warehouse & BI | ||
| │ │ │ └─ Snowflake · BigQuery · Databricks · Looker · Tableau · Power BI | ||
| │ │ ├─ Data pipelines / ELT / CDP | ||
| │ │ │ └─ Fivetran · Airbyte · dbt · Airflow · Kafka · Segment | ||
| │ │ ├─ Feature flags & experimentation | ||
| │ │ │ └─ LaunchDarkly · Split · Optimizely · Statsig | ||
| │ │ ├─ Infrastructure as Code | ||
| │ │ │ └─ Terraform · Pulumi · Ansible · CloudFormation | ||
| │ │ ├─ Cloud security & posture | ||
| │ │ │ └─ Wiz · Prisma Cloud · Aqua · Trivy | ||
| │ │ └─ FinOps / cloud cost | ||
| │ │ └─ Kubecost · CloudHealth · Vantage · AWS Cost Explorer | ||
| │ └─ Cross-cutting (spans all phases) | ||
| │ ├─ Communication / ChatOps | ||
| │ │ └─ Slack · MS Teams · Zoom | ||
| │ ├─ AI models & Agent SDKs | ||
| │ │ └─ model gateways · agent SDKs · Bedrock / Vertex | ||
| │ ├─ Identity & access (SSO/SCIM) | ||
| │ │ └─ Okta · Microsoft Entra ID · Auth0 · Google | ||
| │ ├─ Secrets management | ||
| │ │ └─ HashiCorp Vault · AWS/GCP Secrets Manager · Doppler | ||
| │ └─ Business & GTM (optional scope) | ||
| │ └─ Salesforce · HubSpot · Stripe | ||
| ├─ Constructor Insight | ||
| │ ├─ Cross-vendor data (via Integrations connectors — bound at Workspace ▸ Settings) | ||
| │ ├─ Analytics (renders into Project ▸ Dashboards: delivery health · AI cost · product metrics) | ||
| │ └─ Benchmarking (cost / quality vs industry & peer baselines — scope: Workspace, opt-in Org roll-up) | ||
| ├─ Governance | ||
| │ ├─ Org guardrails & policies | ||
| │ ├─ Access-control policy (org-wide: SSO-required · no-external-sharing · separation-of-duties) | ||
| │ ├─ Audit (org) | ||
| │ ├─ Deployment governance | ||
| │ └─ Data residency & region (Org policy · per-Workspace region) | ||
| └─ Account & Access | ||
| ├─ Users & Access | ||
| │ ├─ Users / People / identity | ||
| │ ├─ SSO / SCIM | ||
| │ ├─ Role definitions (org catalog) | ||
| │ └─ Access control (RBAC / ABAC) | ||
| └─ Billing & Account | ||
| ├─ Subscription plan | ||
| ├─ Billing account | ||
| └─ Usage / AI cost | ||
| ``` | ||
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the workspace we may have objects (work items) which are connected to different projects. So the Project is also an object on the graph. I would say that:
Workspace has objects (work items) - Projects, Documents, Codebase, Incidents, Builds, Pull Requests (all them connected somehow) etc.
Workspace has Flows and Automations
Workspace has Monitoring
Workspace has Audit
Workspace has File browser
Workspace has Membership (teams / people)