Valutazione completata; in attesa di revisione delle prove.
Valutato il 12 maggio 2026 rispetto alla doctrine di AI Design Blueprint
In sviluppo
Stato: Alto rischio
74/100
Voto C
Blueprint Readiness misura l'allineamento alla doctrine, non la runtime correctness. Un verdetto production-ready significa che l'architettura incarna i 10 principi; non esegue i tuoi test o i tuoi tipi. Affiancala alla tua test suite, non sostituirla.
This is an autonomous background orchestration surface with strong persistent job state, explicit approval/blocker handling, and a reproducible audit envelope. Most principles are aligned, but P10 still needs changes: an abort requested during the validating step is acknowledged yet can be ignored, and the retry-onboarding command can erase the failed-step state that approve() needs for safe step-aware recovery.
Storico iterazioni
5 run precedenti su questo artefatto. Ogni run_id apre la sua readiness review.
I punteggi possono salire o scendere tra le iterazioni: il ragionamento del validator non è strettamente deterministico, quindi lo stesso artefatto può ottenere punteggi diversi tra una run e l'altra. I delta per principio più sotto mostrano il cambiamento sostanziale.
Findings per principio
10 principi valutati. Verdict, severity, evidenza e raccomandazione per ognuno. Evidenza e raccomandazione sono nella lingua originale della review, l'inglese.
P10
Richiede modificheBlocker di produzione60/100Ottimizzare per la guida, non solo per l'inizio
The current steering boundary still fails in two concrete paths. First, request_abort() sets abort_requested=True and prints success for any non-terminal job, but _execute_with_job only checks abort_requested before mark_step_started(db, job, "validating"); if an operator aborts while validate_code_against_principles is running, the code proceeds to persist UserValidationRun, set app.validation_run_id, and call mark_completed without refreshing the job or honoring the abort. Second, retry_onboarding_handoff() overwrites app.onboarding_state with "pending", while approve() relies on the captured prior_state being "sign_in_link_failed" or "approval_email_failed" to skip Firebase; using the doc…
Raccomandazione
Move retry and abort authority into a small transactional state-transition boundary. Preserve the failed onboarding step as durable state instead of overwriting it with pending, and add a hard abort check after the validator returns but before persisting or completing the job, or pass a cancellable run token into the worker so abort_requested terminalizes the job as aborted rather than completing it.
P1
AllineatoProgettare per la delega piuttosto che per la manipolazione diretta
Delegation is modeled as assigned work rather than manual execution: approve() gates the applicant handoff, then run_cohort_validate.run creates a persistent CohortValidationJob and _execute_with_job performs cloning, selecting, bundling, validating, and persistence. The user/operator supplies intent through application fields such as repo_url and approval state while the workflow executes the operational steps.
P2
AllineatoAssicurarsi che il lavoro in background rimanga percepibile
Background work is made perceptible through durable CohortValidationJob fields: status, queued_at, cloning_started_at, selecting_started_at, bundling_started_at, validating_started_at, terminal_at, failure_kind, retry_eligible, and abort_requested. _mirror_terminal_to_app also maps terminal job outcomes back to CohortApplication.onboarding_state so the applicant-level record remains inspectable after the worker exits.
P3
AllineatoAllineare il feedback al livello di attenzione dell'utente
Feedback is calibrated by layer: routine progress is represented by concise states such as validation_queued, cloning, validating, completed, blocked, failed, and aborted, while elevated attention paths carry failure_kind, safe_display_message, retry_eligible, and onboarding_failure_reason. _summarize_validate_log deliberately compresses validator logs into high-level signals instead of exposing noisy internals by default.
P4
AllineatoApplicare la divulgazione progressiva all'agenzia del sistema
The code uses progressive disclosure: primary flow state is exposed through CohortApplication.onboarding_state and CohortValidationJob.status, while deeper evidence is stored in audit_object under source, selection, validate, and job. The detailed result is persisted in UserValidationRun.result_json, and _summarize_validate_log avoids dumping raw validation logs into the main status path.
P5
AllineatoSostituire la magia implicita con modelli mentali chiari
The workflow gives a clear mental model through explicit state and boundary names: TERMINAL_STATUSES, FAILURE_KINDS, onboarding states such as firebase_user_failed and approval_email_failed, and operator messages in retry_failed_validation_job explaining non-terminal and non-retryable conditions. The validation bundle is also labeled with BOUNDARY_HEADER and ENVELOPE_ADVISORY, making the untrusted-code boundary explicit.
P6
AllineatoEsporre uno stato operativo significativo, non la complessità interna
Operational state is expressed in actionable terms rather than raw implementation detail: queued, cloning, selecting, bundling, validating, completed, blocked, failed, and aborted. mark_blocked, mark_failed, and _mirror_terminal_to_app translate tool and dependency failures into failure_kind, safe_display_message, retry_eligible, and onboarding_failure_reason fields that support operator action.
P7
AllineatoStabilire fiducia attraverso l'ispezionabilità
Inspectability is supported by a typed reproducibility envelope and audit trail. build_file_envelope records envelope_schema, boundary_contract, advisory, file metadata, and envelope_hash; _build_implementation_context records each selected file's path, byte_size, and sha256; audit_object stores commit_sha, selected_files, skipped_during_read, bundle_sha256, envelope_hash, validator latency, log_signals, and job_id in UserValidationRun.result_json.
P8
AllineatoRendere espliciti i passaggi, le approvazioni e i blocchi
Approvals, handoffs, and blockers are explicit in the main lifecycle. approve() requires an affirmative confirmation unless the operator passes --yes, reject() records a rejection_reason, external handoff failures are typed as firebase_user_failed, sign_in_link_failed, or approval_email_failed, and validation blockers are persisted through mark_blocked with failure_kind and safe_display_message. retry_failed_validation_job also refuses non-terminal or non-retryable jobs with a specific operator-facing explanation.
P9
AllineatoRappresentare il lavoro delegato come un sistema, non solo come una conversazione
Delegated work is represented as a structured system rather than a message stream. CohortValidationJob links application_id, user_id, repo_url, status, step timestamps, retry_count, abort_requested, validation_run_local_id, commit_sha, bundle_sha256, and selection counts; the execution loop is separated from the persisted UserValidationRun result and audit metadata.
Aggiungi al tuo README
Due varianti embeddabili: una piccola e una a card più ricca.
Score card (consigliata)
[](https://aidesignblueprint.com/en/readiness-review/0e49f888-1b71-4cb2-bb86-52327681b997)Badge piatto
[](https://aidesignblueprint.com/en/readiness-review/0e49f888-1b71-4cb2-bb86-52327681b997)Inizia qui, parte 3 di 3
Guarda come nascono questa pagina e il suo badge, dal primo run al README.
ID del run: 0e49f888-1b71-4cb2-bb86-52327681b997
La review di questo artefatto rispetto alla doctrine al momento del run, non un audit di sicurezza né una garanzia sul runtime.
Cosa copre una review e come vengono trattati i dati
Run by agents. Governed by humans. Validated by the AI Design Blueprint.