AI Development FactoryAI Development Factory

The AI Development Factory coordinates several product repositories from one owner-facing operating model. Its central concern is provenance: which repository changed, which commit is current and whether the local machine actually has that revision.The AI Development Factory coordinates several product repositories from one owner-facing operating model. Its central concern is provenance: which repository changed, which commit is current and whether the local machine actually has that revision.

GitHub contains the source history. A single Windows Worker owns the local checkout boundary. The dashboard exists to make that relationship visible instead of hiding it behind generic success messages.GitHub contains the source history. A single Windows Worker owns the local checkout boundary. The dashboard exists to make that relationship visible instead of hiding it behind generic success messages.

This is an owner-operated development environment. It should not be confused with an unattended commercial AI coding service or a guarantee that every product is deployed.This is an owner-operated development environment. It should not be confused with an unattended commercial AI coding service or a guarantee that every product is deployed.

A successful push to GitHub says only that a revision exists in the remote repository. A laptop may be offline, running an older Worker, holding local edits or pointing at a mismatched Git remote.A successful push to GitHub says only that a revision exists in the remote repository. A laptop may be offline, running an older Worker, holding local edits or pointing at a mismatched Git remote.

Blind pulls and destructive cleanups could overwrite work. In multi-project environments, repeated CI and browser-preview execution can also exceed available memory and reduce the reliability of the whole system.Blind pulls and destructive cleanups could overwrite work. In multi-project environments, repeated CI and browser-preview execution can also exceed available memory and reduce the reliability of the whole system.

The Factory therefore needs separate evidence for GitHub state, owner authorization, local synchronization and any manually requested verification.The Factory therefore needs separate evidence for GitHub state, owner authorization, local synchronization and any manually requested verification.

The source defines distinct project states, including active, future, completed and archived. This lets the owner control which repositories belong in the current development cycle.The source defines distinct project states, including active, future, completed and archived. This lets the owner control which repositories belong in the current development cycle.

For active products, the intended Worker flow monitors GitHub heads and attempts guarded fast-forward synchronization when the repository and checkout pass identity and cleanliness checks.For active products, the intended Worker flow monitors GitHub heads and attempts guarded fast-forward synchronization when the repository and checkout pass identity and cleanliness checks.

Completed or archived projects remain discoverable as history without continuously consuming the resources needed by active work.Completed or archived projects remain discoverable as history without continuously consuming the resources needed by active work.

The design favors Git remote validation, branch checks and fast-forward updates instead of reset, stash or clean as automatic recovery techniques. Local tracked and untracked changes are protected from silent replacement.The design favors Git remote validation, branch checks and fast-forward updates instead of reset, stash or clean as automatic recovery techniques. Local tracked and untracked changes are protected from silent replacement.

Legacy path conflicts and ignored files require special care: the existence of two local copies is not permission to delete one. A preserved conflict is a meaningful safety result, not necessarily a broken application.Legacy path conflicts and ignored files require special care: the existence of two local copies is not permission to delete one. A preserved conflict is a meaningful safety result, not necessarily a broken application.

All of these controls must be evaluated against the installed Worker and the actual machine checkout. GitHub source changes alone do not prove that the laptop pulled them.All of these controls must be evaluated against the installed Worker and the actual machine checkout. GitHub source changes alone do not prove that the laptop pulled them.

The Guardian Hub contract describes source-anchored metadata from specialized quality tools, including design, security, API and data, reliability and SEO evaluation.The Guardian Hub contract describes source-anchored metadata from specialized quality tools, including design, security, API and data, reliability and SEO evaluation.

A recorded report is not a substitute for a real scan. When evidence is unavailable the system can report NOT_TESTED; when the source changes, previous evidence can become stale.A recorded report is not a substitute for a real scan. When evidence is unavailable the system can report NOT_TESTED; when the source changes, previous evidence can become stale.

This keeps the dashboard useful as an evidence index without presenting an unrun check or a plugin-written PASS as independently verified release readiness.This keeps the dashboard useful as an evidence index without presenting an unrun check or a plugin-written PASS as independently verified release readiness.

The current October 2026 main-branch policy keeps automatic Worker CI, builds, scans and managed previews disabled. The local Worker is intended to monitor active repositories and perform safe source synchronization within its authorized scope.The current October 2026 main-branch policy keeps automatic Worker CI, builds, scans and managed previews disabled. The local Worker is intended to monitor active repositories and perform safe source synchronization within its authorized scope.

Project code can still be developed directly through reviewed GitHub changes. Expensive or intrusive verification stays a separate, deliberate action rather than silently running on every repository update.Project code can still be developed directly through reviewed GitHub changes. Expensive or intrusive verification stays a separate, deliberate action rather than silently running on every repository update.

Whether a particular machine has installed this revision must be confirmed from fresh owner-device evidence. This case study documents the architecture and policy, not an unverified live deployment.Whether a particular machine has installed this revision must be confirmed from fresh owner-device evidence. This case study documents the architecture and policy, not an unverified live deployment.