Add overview course for Constructor Studio skills

[ainetx]

Summary by CodeRabbit

• Documentation
  • Rebranded README and course materials from “Cyber Fabric” to “Constructor Fabric.”
  • Updated repository links, module titles, learning outcomes, participation paths, and exam/quiz instructions to the new framing.
  • Added a Constructor Studio v1 overview with role-specific narratives, narrator/visual guidance, and production/pacing notes.
  • Revised course maps, adoption guidance, comparison/benefits narratives, and contribution guidance to reflect Constructor Fabric.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Repository branding and course materials are migrated from “Cyber Fabric” to “Constructor Fabric,” updating README and course URLs, rebranding and rewriting course content across modules, and adding a new Constructor Studio v1 overview with six role-specific lesson scripts and production guidance.

Changes

Constructor Fabric Course Branding Migration and Studio Overview

Layer / File(s)	Summary
Repository and source link updates README.md, courses/constructor-studio-draft.md	Top-level README header and draft course source links are rebranded to the constructorfabric namespace and Constructor Fabric terminology.
Constructor Studio v1 course overview and role-specific lessons courses/studio-overview.md	New document introducing Constructor Studio v1 with production framing, six role-specific overviews, time-indexed narrator scripts with animation cues, and closing production/pacing guidance.
Course orientation and early modules courses/constructorfabric-all-course-content.md	Course orientation and early learning-outcome modules are rewritten from Cyber Fabric to Constructor Fabric terminology.
Solution positioning and product map courses/constructorfabric-all-course-content.md	Constructor Fabric positioning, plan-build-run framing, lifecycle connection, and product-map grouping are rewritten with Constructor Fabric terminology.
Three elements and comparisons courses/constructorfabric-all-course-content.md	The three elements module, 'what Constructor Fabric is not', and comparisons with other tools are updated to Constructor Fabric framing.
Unique capabilities and adoption model courses/constructorfabric-all-course-content.md	Unique capability-evaluation guidance and the adoption model (incremental experiments, templates) are converted to Constructor Fabric language.
Participation paths, deeper-dive mapping, and exam courses/constructorfabric-all-course-content.md	Contribution paths, evidence requirements, deeper-dive repo mapping, role-based application paths, and final exam instructions are updated to Constructor Fabric.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 From Cyber to Constructor the lesson threads unwind,
New names and maps, fresh studio scripts align.
Six role-led frames, narrator cues in place,
A fabric renamed, courses dressed with grace.
Hop on—learning stitched with care and pace.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately summarizes the primary change: adding a new overview course file (studio-overview.md) for Constructor Studio. It's clear, concise, and specific to the main contribution.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 5

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

courses/constructorfabric-all-course-content.md (1)

1702-1704: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Replace remaining “Cyber Fabric” references with “Constructor Fabric” for branding consistency.

These lines still use the old brand name inside otherwise rebranded modules, which conflicts with the course migration objective and can confuse learners.

Also applies to: 1808-1810, 2430-2432, 3461-3463

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/constructorfabric-all-course-content.md` around lines 1702 - 1704,
Replace every remaining instance of the old brand string "Cyber Fabric" with
"Constructor Fabric" in the course content (preserve capitalization and
surrounding punctuation), specifically update the occurrence shown in the diff
and the other instances called out (the phrases at the other locations). Search
for the exact token "Cyber Fabric" in the document and perform a global replace,
then run a quick pass to ensure context (sentences mentioning linking
requirements, specifications, code/tests, and CI traceability) reads correctly
after substitution.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@courses/constructor-studio-draft.md`:
- Around line 4-5: Replace the two legacy repo links
"https://github.com/constructorfabric/cyber-constructor" and
"https://github.com/constructorfabric/cyber-constructor-kit-sdlc" with the
canonical repo names used elsewhere:
"https://github.com/constructorfabric/studio" and
"https://github.com/constructorfabric/studio-kit-sdlc"; update the visible repo
name labels (e.g., `cyber-constructor` → `constructorfabric/studio`,
`cyber-constructor-kit-sdlc` → `constructorfabric/studio-kit-sdlc`) and run a
quick grep for any other occurrences of the old repo names to keep
learner-facing docs consistent.

In `@courses/constructorfabric-all-course-content.md`:
- Line 3: The markdown has heading-level jumps and stray spaces inside emphasis
markers (e.g., the "Module overview" heading and other listed headings), causing
markdownlint MD001/MD037 warnings; fix by making heading levels consistent
(adjust number of leading # to follow the surrounding hierarchy for "Module
overview" and the other flagged headings) and remove spaces inside emphasis
markers (change "* text *" or "_ text _" to "*text*" or "_text_") across the
mentioned occurrences so the document conforms to markdownlint rules.
- Line 1392: The markdown link text and its href are inconsistent: the visible
text reads "cyber-constructor-pilot-kit-sdlc" while the href points to
"cyber-pilot-kit-sdlc"; update the link so the display text matches the target
URL (or vice versa) within the markdown link element (the GitHub repository link
in the document) so both the rendered text and the href use the same repository
name.
- Around line 918-919: Split the merged list item "remain.5. Expected
improvement" into two separate, properly punctuated list entries: "Name the
existing tools that remain." and "Expected improvement: State one measurable or
observable benefit." Also fix the ungrammatical phrase "because Constructor
Fabric to make sure..." to a correct form such as "because Constructor Fabric
ensures..." (search for these exact fragments to locate occurrences — apply the
same fixes at the other occurrence noted around lines 2948–2949).

In `@courses/studio-overview.md`:
- Line 43: The course description in courses/studio-overview.md contradicts the
strict validation boundary declared in
courses/constructor-studio-draft-content.md (which states “Constructor Studio
v1.0.0 only”); update the studio-overview wording to match the validated scope
by explicitly stating the course targets Constructor Studio v1.0.0 and will use
the learner-facing terms (Constructor Studio, cfs, cf and workflow skill names
like cf-write-docs, cf-sdlc-doc-prd, cf-sdlc-implement) so the framing does not
imply reuse beyond the validated version boundary.

---

Outside diff comments:
In `@courses/constructorfabric-all-course-content.md`:
- Around line 1702-1704: Replace every remaining instance of the old brand
string "Cyber Fabric" with "Constructor Fabric" in the course content (preserve
capitalization and surrounding punctuation), specifically update the occurrence
shown in the diff and the other instances called out (the phrases at the other
locations). Search for the exact token "Cyber Fabric" in the document and
perform a global replace, then run a quick pass to ensure context (sentences
mentioning linking requirements, specifications, code/tests, and CI
traceability) reads correctly after substitution.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a004f052-2d6f-45b7-b610-74cf21e4b10b

📥 Commits

Reviewing files that changed from the base of the PR and between c58a2f7 and c37dfed.

📒 Files selected for processing (4)

• README.md
• courses/constructor-studio-draft.md
• courses/constructorfabric-all-course-content.md
• courses/studio-overview.md

[Artifizer]

Why we call it Lesson?
For me it should be an overview - a story - like 5 min video at YouTube/Vimeo.
Not lessons

[Artifizer]

I do not like the overall flow at all.

It must be a story, like:

Start with the problem - 30 sec

• there are mid and big size development organizations
• they got significant boost in code and content development with help of LLMs and Agentic tools
• this boost brings new challenge for existing processes, overall control, standartization, etc, especially if ...

Proposed solution - Studio - single environment for different org roles collaboration - Product Managers, Architects, Developers, etc

Explain how it works in 3 min

• There are many tools like X doing Y, but Studio is designed for Z
• Here is how it works ...

[coderabbitai]

🧹 Nitpick comments (1)

courses/studio-overview.md (1)

48-48: ⚡ Quick win

Clarify what "router-level workflow names" means.

The constraint says not to mention these in scripts, but the production team may not know what qualifies as a router-level workflow name versus a learner-facing skill. Consider adding an example or brief definition so the constraint is unambiguous.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/studio-overview.md` at line 48, Update the constraint text that
currently says "Do not mention router-level workflow names in learner-facing
video scripts" to define what a router-level workflow name is and provide an
example contrast with a learner-facing skill; specifically, add a short
parenthetical or sentence that explains "router-level workflow names" are
internal routing/engine identifiers (e.g., internal workflow IDs or system step
names like "onboarding_router_v2" or "assign_route_task") and show a brief
example of a learner-facing skill name (e.g., "Completing Your First Project")
so teams can clearly distinguish which terms are disallowed in scripts and which
are acceptable.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@courses/studio-overview.md`:
- Line 48: Update the constraint text that currently says "Do not mention
router-level workflow names in learner-facing video scripts" to define what a
router-level workflow name is and provide an example contrast with a
learner-facing skill; specifically, add a short parenthetical or sentence that
explains "router-level workflow names" are internal routing/engine identifiers
(e.g., internal workflow IDs or system step names like "onboarding_router_v2" or
"assign_route_task") and show a brief example of a learner-facing skill name
(e.g., "Completing Your First Project") so teams can clearly distinguish which
terms are disallowed in scripts and which are acceptable.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0cc9ffaa-b314-4fe3-9f5d-ad24703946bb

📥 Commits

Reviewing files that changed from the base of the PR and between c37dfed and e555abb.

📒 Files selected for processing (1)

• courses/studio-overview.md

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

courses/constructorfabric-all-course-content.md (1)

1352-1352: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix typo in repository name.

"cybereare-frontx" contains a typo and should be "cyberware-frontx" (or possibly "frontx" based on other references).

✏️ Proposed fix

-| Ware UI, docs, and standards | cybereare-frontx, DNA | Inspect these when you want to understand UI, development principles, guidelines, and instructions for multi-tenant SaaS platform and application development. |
+| Ware UI, docs, and standards | cyberware-frontx, DNA | Inspect these when you want to understand UI, development principles, guidelines, and instructions for multi-tenant SaaS platform and application development. |

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/constructorfabric-all-course-content.md` at line 1352, There is a
typo in the repository name string "cybereare-frontx" within the table row
labeled "Ware UI, docs, and standards"; update that token to the correct
repository name (replace "cybereare-frontx" with "cyberware-frontx" or the
canonical "frontx" if other references use that form) so it matches existing
repo references and project conventions.

♻️ Duplicate comments (4)

courses/constructorfabric-all-course-content.md (3)

918-919: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix merged list item that breaks readability.

Line 918 contains a merged list item: "Name the existing tools that remain.5. Expected improvement" should be split into two separate entries with proper formatting.

✏️ Proposed fix

-Name the existing tools that remain.5. Expected improvement\
+Name the existing tools that remain.\
+**5. Expected improvement**\

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/constructorfabric-all-course-content.md` around lines 918 - 919,
Split the merged list item "Name the existing tools that remain.5. Expected
improvement" into two separate, properly formatted list entries: one for "Name
the existing tools that remain." and a new one for "Expected improvement" (e.g.,
prefix both with list markers like "-" or "1."/"2." consistent with surrounding
list style). Ensure punctuation/spacing is corrected so each item appears on its
own line and matches the surrounding markdown list formatting.

---

2948-2949: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix ungrammatical sentence construction.

The phrase "because Constructor Fabric to make sure that confusion is reduced" is grammatically incorrect. The infinitive "to make sure" doesn't fit after "because Constructor Fabric".

✏️ Proposed fix

-Furthermore, the wording should reflect the products and the architecture
-of the Github repositories because Constructor Fabric to make sure that
-confusion is reduced.
+Furthermore, the wording should reflect the products and the architecture
+of the GitHub repositories to ensure Constructor Fabric concepts are
+clearly communicated and confusion is reduced.

Note: Also corrected "Github" to "GitHub" (proper capitalization).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/constructorfabric-all-course-content.md` around lines 2948 - 2949,
Replace the ungrammatical fragment "because Constructor Fabric to make sure that
confusion is reduced" with a correct clause and fix GitHub capitalization; for
example change the sentence to "of the GitHub repositories so that confusion is
reduced" (or "to ensure that confusion is reduced") by locating the phrase
"because Constructor Fabric to make sure that confusion is reduced" in the
document and updating it accordingly.

---

1392-1392: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix repository link text mismatch.

The display text shows "cyber-constructor-pilot-kit-sdlc" but the actual URL points to "cyber-pilot-kit-sdlc". Based on line 1348 and other references in the document, the correct repository name appears to be "cyber-pilot-kit-sdlc".

🔗 Proposed fix

-**Repository: **[https://github.com/constructorfabric/cyber-constructor-pilot-kit-sdlc](https://github.com/constructorfabric/cyber-pilot-kit-sdlc)
+**Repository: **[https://github.com/constructorfabric/cyber-pilot-kit-sdlc](https://github.com/constructorfabric/cyber-pilot-kit-sdlc)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/constructorfabric-all-course-content.md` at line 1392, Fix the
mismatched repository link text: update the Markdown link whose URL is
https://github.com/constructorfabric/cyber-pilot-kit-sdlc so the display text
reads "cyber-pilot-kit-sdlc" (matching the URL and other references) instead of
"cyber-constructor-pilot-kit-sdlc"; ensure any other occurrences in this
document that reference the same repo use the consistent "cyber-pilot-kit-sdlc"
display text.

courses/studio-overview.md (1)

30-30: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Version boundary needs explicit v1.0.0 statement.

Line 30 states "Constructor Studio v1" generically, but the validation contract in other course files specifies "Constructor Studio v1.0.0 only." To avoid implying the scripts apply to all v1.x versions beyond the validated scope, update this line to explicitly reference v1.0.0.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@courses/studio-overview.md` at line 30, The document currently refers to
"Constructor Studio v1" ambiguously; update that phrasing in the sentence that
reads "Constructor Studio v1" to explicitly state "Constructor Studio v1.0.0" so
the script pack aligns with the validation contract used elsewhere (replace the
exact phrase "Constructor Studio v1" with "Constructor Studio v1.0.0").

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@courses/constructorfabric-all-course-content.md`:
- Around line 1591-1592: Update the mismatched repo display text so it matches
the URL: replace the label "cyberware-csharp" with
"constructorfabric-core-csharp" (or alternatively update the URL to match the
intended "cyberware-csharp" repo) in the markdown entry that currently shows the
link <https://github.com/constructorfabric/constructorfabric-core-csharp>,
ensuring the visible text and the target URL are consistent.
- Line 1205: The link text for "ConstructorFabric Core" is pointing to the wrong
repo: the anchor text currently references constructorfabric/cyberware-rust
while the href targets constructorfabric/constructorfabric-core; update the
markdown so the display text and the href are consistent by changing the anchor
text (or href) to reference constructorfabric/constructorfabric-core wherever
"ConstructorFabric Core" appears (specifically the mismatched link entry),
leaving spacing unchanged.

---

Outside diff comments:
In `@courses/constructorfabric-all-course-content.md`:
- Line 1352: There is a typo in the repository name string "cybereare-frontx"
within the table row labeled "Ware UI, docs, and standards"; update that token
to the correct repository name (replace "cybereare-frontx" with
"cyberware-frontx" or the canonical "frontx" if other references use that form)
so it matches existing repo references and project conventions.

---

Duplicate comments:
In `@courses/constructorfabric-all-course-content.md`:
- Around line 918-919: Split the merged list item "Name the existing tools that
remain.5. Expected improvement" into two separate, properly formatted list
entries: one for "Name the existing tools that remain." and a new one for
"Expected improvement" (e.g., prefix both with list markers like "-" or
"1."/"2." consistent with surrounding list style). Ensure punctuation/spacing is
corrected so each item appears on its own line and matches the surrounding
markdown list formatting.
- Around line 2948-2949: Replace the ungrammatical fragment "because Constructor
Fabric to make sure that confusion is reduced" with a correct clause and fix
GitHub capitalization; for example change the sentence to "of the GitHub
repositories so that confusion is reduced" (or "to ensure that confusion is
reduced") by locating the phrase "because Constructor Fabric to make sure that
confusion is reduced" in the document and updating it accordingly.
- Line 1392: Fix the mismatched repository link text: update the Markdown link
whose URL is https://github.com/constructorfabric/cyber-pilot-kit-sdlc so the
display text reads "cyber-pilot-kit-sdlc" (matching the URL and other
references) instead of "cyber-constructor-pilot-kit-sdlc"; ensure any other
occurrences in this document that reference the same repo use the consistent
"cyber-pilot-kit-sdlc" display text.

In `@courses/studio-overview.md`:
- Line 30: The document currently refers to "Constructor Studio v1" ambiguously;
update that phrasing in the sentence that reads "Constructor Studio v1" to
explicitly state "Constructor Studio v1.0.0" so the script pack aligns with the
validation contract used elsewhere (replace the exact phrase "Constructor Studio
v1" with "Constructor Studio v1.0.0").

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4ecfa525-56ae-4207-b521-19caee00ce1d

📥 Commits

Reviewing files that changed from the base of the PR and between e555abb and d40b5bd.

📒 Files selected for processing (4)

• README.md
• courses/constructor-studio-draft.md
• courses/constructorfabric-all-course-content.md
• courses/studio-overview.md

✅ Files skipped from review due to trivial changes (2)

• README.md
• courses/constructor-studio-draft.md

[Artifizer]

I'm not sure I got the idea about single chat. I think it's not the case even for small organizations

[Artifizer]

The 'prison' term sounds aggressive

[Artifizer]

I'd have a section that Studio doesn't change your technological stack and works on top of your favorite AI tools - claude code, github copilot, cursor and such. This is important, because teams do not want to change the wheels just because of one more tool

[Artifizer]

Role lanes call specific skills only after the problem is introduced

I did not get the idea

[Artifizer]

Canonical Provenance Trace IDs (or just CPT ID)

[Artifizer]

Adoption does not require a process reset
->
Adoption does not require a process, tech stack or favorite tools reset.

[Artifizer]

I think we must not use PRD and ADR in speech, only Product Requirements Document and Architecture Decision Records

[Artifizer]

more stable than a chat transcript
->
more stable than a chat transcript or an unstructured requirements document

[Artifizer]

I think we need to focus more on that traceability and linking system, visualize it:

1. Studio maintains traceability system that allows to understand what parts of the requirements where covered by the design and how exactly it can be implemented. It helps AI to update needed parts of the design or code if requirements changed or identify the gaps

2. Product Managers can link new requirements, or specific paragraphs within them, to requirements defined elsewhere by using stable IDs. This makes it possible to build a graph of connected requirements that shapes the final product scope.

[Artifizer]

folders?

[Artifizer]

Evidence cards?

[Artifizer]

I think we also need to address another common challenge for architects: architecture is typically a tradeoff between business requirements, technical constraints, future extensibility, operational costs, security, and performance.

1. Architects need to consider many different inputs to make the right decisions. Studio helps keep all of those inputs accessible and provides capabilities such as architecture document templates, validation rules, and other mechanisms that support consistent, well-informed decision-making.

2. Studio inherits modern architecture documentation practices by separating Design documents from Architecture Decision Records. Design documents define how the system should work, while ADRs capture why specific decisions were made. This separation reduces AI context size by isolating the pure Design content needed for code generation from ADRs, which preserve architectural history and rationale but are not required in the code generation context.

[Artifizer]

We should also mention phase tags for requirement stories.

Studio provides a simple phase-tagging system that groups requirements by delivery phase. This helps architects understand the full product direction in advance by seeing both current requirements and upcoming functionality, while allowing development teams to stay focused on the current delivery scope.

[Artifizer]

chat summary?

[Artifizer]

Other valuable features:

1. Gap analysis between requirement and real implementation, with help of traceable requirements IDs

The Workspaces is not covered:

2. Allows to oversee other repositories with the specs and code to trace consistency, make gap analysis and traceabilty between different parts of the system - documentation, libraries & components source code - API contracts, front, backend components, mobile app, etc.

[Artifizer]

Need to mention real example - Studio allows to review requirements and check where certain requirements being tested - unit tests, integration tests, end-to-end tests, security tests, performance tests, etc. Studio provides workspace management for multi-repository management and gap analysis capabilities

[il10241024]

how about product managers?

[il10241024]

and product managers and (in the future UX designers)

[il10241024]

better explain which integrations you are talking about.
also above "Host Integrations" term was introduced but not explained

[il10241024]

better specify somewhere on top - which project/artefact a student will work on.
or it's a student duty to define project?

[il10241024]

Commented