Repository navigation
Establish explainable automation control plane v1 - #1
Conversation
|
The draft now includes an explainable lead-generation and marketing proposal layer. This addition does not place marketing modules into production sites. It establishes a governed review path in which each repository supplies a proposal generator, the control plane validates every idea against a shared schema, complete proposal and mockup packages are retained as workflow artifacts, and a review issue can be assigned to A valid package must separate observations from inference; identify the audience, need, journey position, value exchange, conversion mechanism, implementation boundary, alternatives, risks, and unknowns; define responsive and interaction states; specify analytics events, denominator, lead-quality measure, guardrails, and stopping conditions; and document privacy, consent, accessibility, provider, and data-retention implications. The schema explicitly records that implementation and production are not authorized by proposal generation. The reusable workflow requires each package to contain The caller example shows a twice-monthly schedule and manual trigger. It assigns proposal review to |
This draft establishes the organization-level automation control plane without changing production deployments or repository protections.
The change introduces an explainable hybrid architecture: shared permission, evidence, artifact, promotion, and exception semantics remain central, while each repository declares its own build and verification contract. The documentation explains why this boundary was chosen, how assumptions are reviewed, how controls progress from observation to enforcement, and how rollback works through version pins.
The initial machine-readable layer contains a repository automation manifest schema and conservative policy defaults for least privilege, frozen installations, artifact promotion, pull-request-based source mutation, expiring exceptions, and restricted agent authority.
The first executable workflow is reusable Node web verification. It requires an explicit build command, refuses unsupported package-manager contracts, installs from frozen lockfiles, reports missing test surfaces rather than implying they passed, records execution identity, computes an artifact digest, and retains the verified artifact. The workflow is intentionally verification-only. It does not deploy, mutate source, change secrets, or write across repositories.
Review should focus on whether the policy boundary is appropriately conservative, whether the repository schema captures enough context without becoming implementation-specific, and whether the reusable workflow produces evidence that can support later visual-design automation and agent-runtime controls.
After this control-plane PR is accepted, the next change should adopt it in representative canary repositories through repository-local manifests and thin caller workflows. Production enforcement should follow only after observational runs establish stable baselines.