incubator

Incubator

Incubator is the working repository for technical research, design notes, implementation spikes, and recurring insight reports produced for ongoing topics.

The repository is organized around two durable output lanes:

• daily/ for recurring daily insight reports.
• artifacts/ for topic-scoped work units, where each topic is managed in its own home directory.

This repository is intended to stay practical and extensible: new work should fit the existing layout without requiring a new top-level convention for every request.

Repository Structure

daily/

daily/ stores recurring daily insight reports, currently generated by the daily-news workflow on a date-based schedule.

Expected pattern:

• daily/YYYY-MM/AgentK_Daily_Insight_YYYY-MM-DD.md

Use daily/ for:

• scheduled daily news summaries
• recurring date-indexed reports
• operational insight logs that are naturally grouped by date

Do not use daily/ for ad hoc project work or topic-specific implementation artifacts.

artifacts/

artifacts/ stores topic-based work units. Each topic should have its own home under artifacts/<topic-home>/ and should keep its research, specifications, implementation notes, and status updates scoped to that directory.

Use artifacts/ for:

• technical investigations
• research reports and comparative studies
• implementation spikes and prototypes
• design documents, PRDs, ADRs, and status trackers
• follow-up revisions to an existing topic

Operating rule:

• New request on a new topic -> create a new topic home under artifacts/
• Follow-up work on an existing topic -> continue inside the existing topic home unless an explicit restructure is requested

scripts/

scripts/ contains repository automation and support tooling used to generate, validate, or publish repository outputs.

Working Model

This repository is maintained as a long-lived documentation and artifact store rather than a single product codebase.

When adding or updating content:

1. Identify whether the output belongs to daily/ or artifacts/.
2. If the work is topic-based, locate the existing topic home or create a new one.
3. Keep related materials inside the same topic home so follow-up work remains traceable.
4. Update index or status documents when the repository structure changes materially.

Publishing and Automation

• Daily insight generation is handled by the daily-news workflow.
• Topic artifacts are committed as normal repository content.
• GitHub Pages or other publishing surfaces may expose selected content, but repository structure should remain useful even without a publishing layer.

Related Indexes

• artifacts/index.md
• daily/index.md
• CONTRIBUTING.md
• WORKLOG.md