spike(framework): validate a portable project-policy boundary

Aperta
#585 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
cli, tooling

Direzione di ricerca

Start by mapping the existing .aidd/ state and the aidd clean --force entry point, including auth, manifests, caches, ignore rules, secrets, and generated files. Review the stale .aidd/config.yml documentation, then compare at least two live policy consumers and candidate boundaries. Done means a written decision, cleanup and credential-safety evidence, an owner for documentation correction, and justified follow-up work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Question

What portable project-policy boundary, if any, lets a team version genuinely shared AI-development policy without colliding with CLI-managed state or a specific host?

Why this must be investigated first

.aidd/ already contains CLI-managed auth, manifests, and caches. aidd clean --force currently removes the whole directory. The previous proposal assumed .aidd/config.yml, YAML, precedence, and a broad schema before proving the consumers or a safe ownership boundary.

Scope

  • Map the lifecycle and ownership of existing project state, including clean, ignore, secrets, and generated files.
  • Establish at least two independent, live policy consumers that cannot be served by existing project documentation, rules, or host configuration.
  • Compare candidate locations and formats against portability, team review, lifecycle safety, and host neutrality.
  • Decide whether a shared policy artifact is warranted; if so, recommend its narrowest first contract and migration safeguards.

Evidence of completion

  • A written decision records the candidate consumers, alternatives considered, and rejected options.
  • The chosen boundary is not deleted by normal CLI cleanup and cannot expose credentials through normal version control.
  • Any required correction to the stale config.yml documentation is identified with an owner.
  • The result names follow-up delivery work only when the evidence justifies it.

Out of scope

  • Implementing a parser, schema, generator, precedence cascade, or consumers.
  • Choosing YAML in advance.
  • Migrating existing runtime configuration or secrets.
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
14h 36m
PR unite (30g)
110

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.