diff --git a/ProjectIntakeTower/explainers/web/neurips2025-5af2132635.html b/ProjectIntakeTower/explainers/web/neurips2025-5af2132635.html new file mode 100644 index 0000000000000000000000000000000000000000..b0cbbd20136763f4adfc915f4e804fb685ad9aea --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-5af2132635.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-5af2132635.md · Video: neurips2025-5af2132635.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-6478fd35c7.html b/ProjectIntakeTower/explainers/web/neurips2025-6478fd35c7.html new file mode 100644 index 0000000000000000000000000000000000000000..1e34de78e485d1389b67df0b3e6d30ae316ef018 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-6478fd35c7.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-6478fd35c7.md · Video: neurips2025-6478fd35c7.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-67a2662309.html b/ProjectIntakeTower/explainers/web/neurips2025-67a2662309.html new file mode 100644 index 0000000000000000000000000000000000000000..41bffd8863a9c34d087e3599aa1460283ee2294d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-67a2662309.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-67a2662309.md · Video: neurips2025-67a2662309.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-7e9bb70151.html b/ProjectIntakeTower/explainers/web/neurips2025-7e9bb70151.html new file mode 100644 index 0000000000000000000000000000000000000000..a5daa1767b5e497a206f96654d806f741841708e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-7e9bb70151.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-7e9bb70151.md · Video: neurips2025-7e9bb70151.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-81e4986b81.html b/ProjectIntakeTower/explainers/web/neurips2025-81e4986b81.html new file mode 100644 index 0000000000000000000000000000000000000000..5de94ed7b468d8a7d48d2bc21def67bec143ef31 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-81e4986b81.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-81e4986b81.md · Video: neurips2025-81e4986b81.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-8dff640782.html b/ProjectIntakeTower/explainers/web/neurips2025-8dff640782.html new file mode 100644 index 0000000000000000000000000000000000000000..1b81f4e4cb3ed4d10249df70ba6b00082ee6a6a2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-8dff640782.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-8dff640782.md · Video: neurips2025-8dff640782.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-c2ff3ffd6b.html b/ProjectIntakeTower/explainers/web/neurips2025-c2ff3ffd6b.html new file mode 100644 index 0000000000000000000000000000000000000000..795400152d3936a9b2e4440eb334e9d1a410b536 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-c2ff3ffd6b.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-c2ff3ffd6b.md · Video: neurips2025-c2ff3ffd6b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-c860dc542c.html b/ProjectIntakeTower/explainers/web/neurips2025-c860dc542c.html new file mode 100644 index 0000000000000000000000000000000000000000..9e40687e8178377c5c5fa8896e3ceaf1b0573ebd --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-c860dc542c.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-c860dc542c.md · Video: neurips2025-c860dc542c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/neurips2025-d829d822f4.html b/ProjectIntakeTower/explainers/web/neurips2025-d829d822f4.html new file mode 100644 index 0000000000000000000000000000000000000000..341b21dab6e826546ae86c50a10d819cd9574e46 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/neurips2025-d829d822f4.html @@ -0,0 +1,6 @@ +neurips2025 — Visual Explainer

ProjectIntakeTower Visual Explainer

neurips2025

/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/neurips2025

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: neurips2025-d829d822f4.md · Video: neurips2025-d829d822f4.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/nimble_options-cc308466fd.html b/ProjectIntakeTower/explainers/web/nimble_options-cc308466fd.html new file mode 100644 index 0000000000000000000000000000000000000000..8a67d5928d3e788c54c36042a7b079d749a68697 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/nimble_options-cc308466fd.html @@ -0,0 +1,6 @@ +nimble_options — Visual Explainer

ProjectIntakeTower Visual Explainer

nimble_options

/home/smlflg/Projekte/symphony/elixir/deps/nimble_options

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

NimbleOptions [Online Documentation][docs].

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_options/CHANGELOG.md:75 — * Fix a small bug with docs for nested schemas.
+

Storyboard: nimble_options-cc308466fd.md · Video: nimble_options-cc308466fd.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/nimble_pool-a86c15bd7c.html b/ProjectIntakeTower/explainers/web/nimble_pool-a86c15bd7c.html new file mode 100644 index 0000000000000000000000000000000000000000..912787ce2491995cc36975d0546b9256b939eb1e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/nimble_pool-a86c15bd7c.html @@ -0,0 +1,6 @@ +nimble_pool — Visual Explainer

ProjectIntakeTower Visual Explainer

nimble_pool

/home/smlflg/Projekte/symphony/elixir/deps/nimble_pool

Tech: docs/notes · Score: 16 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

NimblePool <!-- MDOC !--> `NimblePool` is a tiny resource-pool implementation.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 5 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 5 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_pool/README.md:85 — port = Port.open({:spawn_executable, path}, [:binary, args: ["-"]])
  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_pool/README.md:158 — if Mint.HTTP1.open?(conn) do
  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_pool/README.md:193 — # TODO: Add back-off
  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_pool/CHANGELOG.md:13 — * Fix a bug on idle timeout causing the pool to empty
  • /home/smlflg/Projekte/symphony/elixir/deps/nimble_pool/CHANGELOG.md:22 — * Fix a bug with lazy pool starting more connections than specified
+

Storyboard: nimble_pool-a86c15bd7c.md · Video: nimble_pool-a86c15bd7c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/notebooks-580f1cdfe4.html b/ProjectIntakeTower/explainers/web/notebooks-580f1cdfe4.html new file mode 100644 index 0000000000000000000000000000000000000000..a03d5af0aaa210d57c5605f5c2f8c566b1931d58 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/notebooks-580f1cdfe4.html @@ -0,0 +1,6 @@ +notebooks — Visual Explainer

ProjectIntakeTower Visual Explainer

notebooks

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/examples/notebooks

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

This directory contains `IPython`_ Notebooks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/examples/notebooks/README.txt:1 — This directory contains `IPython`_ Notebooks. To open them, run ``ipython
+

Storyboard: notebooks-580f1cdfe4.md · Video: notebooks-580f1cdfe4.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/null-0be625c78a.html b/ProjectIntakeTower/explainers/web/null-0be625c78a.html new file mode 100644 index 0000000000000000000000000000000000000000..326c6f8948f154a1ebc41bb3e29a716562b6bac8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/null-0be625c78a.html @@ -0,0 +1,6 @@ +null — Visual Explainer

ProjectIntakeTower Visual Explainer

null

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 16 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 16 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/cds/null/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: null-0be625c78a.md · Video: null-0be625c78a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/null-8b19112639.html b/ProjectIntakeTower/explainers/web/null-8b19112639.html new file mode 100644 index 0000000000000000000000000000000000000000..733e0a7a55479abf1179b3cbc2117475ff909242 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/null-8b19112639.html @@ -0,0 +1,6 @@ +null — Visual Explainer

ProjectIntakeTower Visual Explainer

null

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 16 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 16 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/cds/null/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: null-8b19112639.md · Video: null-8b19112639.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/null-ce13fe3502.html b/ProjectIntakeTower/explainers/web/null-ce13fe3502.html new file mode 100644 index 0000000000000000000000000000000000000000..abb86d742892f76ea1c0c7f294001712828aa9f4 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/null-ce13fe3502.html @@ -0,0 +1,6 @@ +null — Visual Explainer

ProjectIntakeTower Visual Explainer

null

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 16 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 16 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/cds/null/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: null-ce13fe3502.md · Video: null-ce13fe3502.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/old-93baf0afb0.html b/ProjectIntakeTower/explainers/web/old-93baf0afb0.html new file mode 100644 index 0000000000000000000000000000000000000000..ed6aad8cb5a57baaf903f55dcb37ba0a7b4289dc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/old-93baf0afb0.html @@ -0,0 +1,6 @@ +old — Visual Explainer

ProjectIntakeTower Visual Explainer

old

/home/smlflg/Projekte/WerBinIch/archive/old

Tech: python · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Who Am I CLI Minimal two-agent "Who am I?" CLI game using OpenAI-compatible chat completions.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/WerBinIch/archive/old/whoami_game.py:91 — "Ask the next useful yes/no question or make a guess."
+

Storyboard: old-93baf0afb0.md · Video: old-93baf0afb0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/openai_like-1e18cd340c.html b/ProjectIntakeTower/explainers/web/openai_like-1e18cd340c.html new file mode 100644 index 0000000000000000000000000000000000000000..3e0c2cf6d0c18adfb2f69e82f41133425e7d09e9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/openai_like-1e18cd340c.html @@ -0,0 +1,6 @@ +openai_like — Visual Explainer

ProjectIntakeTower Visual Explainer

openai_like

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/openai_like

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

JSON-Based OpenAI-Compatible Provider Configuration This directory contains the new JSON-based configuration system for OpenAI-compatible providers.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/openai_like/json_loader.py:47 — with open(json_path) as f:
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/openai_like/common_utils.py:48 — ): # [TODO] remove 'validate_environment' from OpenAI base. should use llm providers config for this only.
+

Storyboard: openai_like-1e18cd340c.md · Video: openai_like-1e18cd340c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/openclaude-3a3b9d4a36.html b/ProjectIntakeTower/explainers/web/openclaude-3a3b9d4a36.html new file mode 100644 index 0000000000000000000000000000000000000000..768cf6dee154fa950318f328fb5a4d9541c9a658 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/openclaude-3a3b9d4a36.html @@ -0,0 +1,6 @@ +openclaude — Visual Explainer

ProjectIntakeTower Visual Explainer

openclaude

/home/smlflg/Projekte/derWolfimSchafspelz/openclaude

Tech: docker, node, typescript · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

OpenClaude OpenClaude is an open-source coding-agent CLI for cloud and local model providers.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/CONTRIBUTING.md:5 — OpenClaude is a fast-moving open-source coding-agent CLI with support for multiple providers, local backends, MCP, and a terminal-first workflow. The best contributions here are fo
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/CONTRIBUTING.md:12 — - For larger changes, open an issue first so the scope is clear before implementation.
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/CODE_OF_CONDUCT.md:12 — We pledge to act and interact in ways that contribute to an open, welcoming,
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/SECURITY.md:5 — Open Claude is currently maintained on the latest `main` branch and the latest
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/SECURITY.md:14 — Security fixes are generally released in the next patch version and may also be
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/SECURITY.md:19 — If you believe you have found a security vulnerability in Open Claude, please
+

Storyboard: openclaude-3a3b9d4a36.md · Video: openclaude-3a3b9d4a36.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/openclaude-vscode-7443330dc2.html b/ProjectIntakeTower/explainers/web/openclaude-vscode-7443330dc2.html new file mode 100644 index 0000000000000000000000000000000000000000..125bf4b60ff23c9919405d71a2d3ed6d47a089c5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/openclaude-vscode-7443330dc2.html @@ -0,0 +1,6 @@ +openclaude-vscode — Visual Explainer

ProjectIntakeTower Visual Explainer

openclaude-vscode

/home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode

Tech: node · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

OpenClaude VS Code Extension A practical VS Code companion for OpenClaude with a project-aware **Control Center**, predictable terminal launch behavior, and quick access to useful OpenClaude workflows.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:18 — - avoids launching from an arbitrary default cwd when a project is open
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:22 — - Open Workspace Profile
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:23 — - Open Repository
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:24 — - Open Setup Guide
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:25 — - Open Command Palette
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/vscode-extension/openclaude-vscode/README.md:35 — - `OpenClaude: Open Control Center`
+

Storyboard: openclaude-vscode-7443330dc2.md · Video: openclaude-vscode-7443330dc2.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/openclaw-brandops-b4d7e01139.html b/ProjectIntakeTower/explainers/web/openclaw-brandops-b4d7e01139.html new file mode 100644 index 0000000000000000000000000000000000000000..3dae933cef6d0101822c0c71ce524b1ca55ebb57 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/openclaw-brandops-b4d7e01139.html @@ -0,0 +1,6 @@ +openclaw-brandops — Visual Explainer

ProjectIntakeTower Visual Explainer

openclaw-brandops

/home/smlflg/Projekte/BrandOps/packages/openclaw-brandops

Tech: node · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/BrandOps/packages/openclaw-brandops/src/brandops-state.js:89 — ## Next Step
  • /home/smlflg/Projekte/BrandOps/packages/openclaw-brandops/src/brandops-state.js:124 — metric: "97.3% accuracy (36/37), 148/148 tests pass, fail-open hook design",
  • /home/smlflg/Projekte/BrandOps/packages/openclaw-brandops/src/brandops-state.js:128 — nextStep: "Pull one concrete screenshot from PortfolioTimeline and one README-ready metric block into the next published clip.",
  • /home/smlflg/Projekte/BrandOps/packages/openclaw-brandops/src/brandops-state.js:157 — nextStep: "Pull one short screen capture or still from the runtime switch and difference map into the next public clip so the proof reads instantly in feeds.",
+

Storyboard: openclaw-brandops-b4d7e01139.md · Video: openclaw-brandops-b4d7e01139.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/opencode-46ba2b8c1e.html b/ProjectIntakeTower/explainers/web/opencode-46ba2b8c1e.html new file mode 100644 index 0000000000000000000000000000000000000000..3e73b63e7647aebb56b5fb6760c9c88652b0bd97 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/opencode-46ba2b8c1e.html @@ -0,0 +1,6 @@ +opencode — Visual Explainer

ProjectIntakeTower Visual Explainer

opencode

/home/smlflg/Projekte/Zentrale/projects/smoke-test/context-packs/implementation/opencode

Tech: agent · Score: 14 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein lokales Kontroll-Cockpit für Agenten, Projekte, Sessions, Handoffs und operative Übersicht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • agentized

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Zentrale/projects/smoke-test/context-packs/implementation/opencode/HERMES.md:5 — Focus on ambiguous work, fallback diagnosis, and clear next actions.
  • /home/smlflg/Projekte/Zentrale/projects/smoke-test/context-packs/implementation/opencode/CODEX.md:5 — Focus on plan refinement, review, repair instructions, and verification discipline.
+

Storyboard: opencode-46ba2b8c1e.md · Video: opencode-46ba2b8c1e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/opencodegousagedashboard-99e39ee7a3.html b/ProjectIntakeTower/explainers/web/opencodegousagedashboard-99e39ee7a3.html new file mode 100644 index 0000000000000000000000000000000000000000..b854a7538efada6085fd884eeea92b319641ffac --- /dev/null +++ b/ProjectIntakeTower/explainers/web/opencodegousagedashboard-99e39ee7a3.html @@ -0,0 +1,6 @@ +OpenCodeGoUsageDashboard — Visual Explainer

ProjectIntakeTower Visual Explainer

OpenCodeGoUsageDashboard

/home/smlflg/Projekte/OpenCodeGoUsageDashboard

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein lokales Kontroll-Cockpit für Agenten, Projekte, Sessions, Handoffs und operative Übersicht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: opencodegousagedashboard-99e39ee7a3.md · Video: opencodegousagedashboard-99e39ee7a3.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/outputs-6b6a7d55d9.html b/ProjectIntakeTower/explainers/web/outputs-6b6a7d55d9.html new file mode 100644 index 0000000000000000000000000000000000000000..25a837401b538563c79718ced3c0d59c34dbbe98 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/outputs-6b6a7d55d9.html @@ -0,0 +1,6 @@ +outputs — Visual Explainer

ProjectIntakeTower Visual Explainer

outputs

/home/smlflg/Projekte/Amazon/outputs

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Amazon Derivatives Analysis Outputs Generated for 2026-01-01 to 2026-04-14.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Amazon/outputs/amazon_costs.md:33 — - Die Kosten laufen primär über das Finanzierungslevel. Bei Open-End-Turbos wird der Basispreis/Finanzierungslevel typischerweise angepasst.
+

Storyboard: outputs-6b6a7d55d9.md · Video: outputs-6b6a7d55d9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-0c30f29722.html b/ProjectIntakeTower/explainers/web/p5js-0c30f29722.html new file mode 100644 index 0000000000000000000000000000000000000000..e9a3228509d2d1155506028a712f7ec8bb21f917 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-0c30f29722.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-0c30f29722.md · Video: p5js-0c30f29722.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-0ee51dd18a.html b/ProjectIntakeTower/explainers/web/p5js-0ee51dd18a.html new file mode 100644 index 0000000000000000000000000000000000000000..e849ecfd016a731a57f857637fbc10b2014fe0e8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-0ee51dd18a.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-0ee51dd18a.md · Video: p5js-0ee51dd18a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-466e082c5a.html b/ProjectIntakeTower/explainers/web/p5js-466e082c5a.html new file mode 100644 index 0000000000000000000000000000000000000000..256498040e0ddf55e6c65638b674435046869866 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-466e082c5a.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-466e082c5a.md · Video: p5js-466e082c5a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-48018de1f0.html b/ProjectIntakeTower/explainers/web/p5js-48018de1f0.html new file mode 100644 index 0000000000000000000000000000000000000000..42de507e54bf40507a1fe49f6306e80e3cc72be5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-48018de1f0.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/mlg/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-48018de1f0.md · Video: p5js-48018de1f0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-5ed30c1ba1.html b/ProjectIntakeTower/explainers/web/p5js-5ed30c1ba1.html new file mode 100644 index 0000000000000000000000000000000000000000..256066ab3e595300b996311b89eda7cea225e937 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-5ed30c1ba1.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/ra/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/ra/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-5ed30c1ba1.md · Video: p5js-5ed30c1ba1.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-8cf8af2cc5.html b/ProjectIntakeTower/explainers/web/p5js-8cf8af2cc5.html new file mode 100644 index 0000000000000000000000000000000000000000..849631f0e0409952ed7b0de8d766be80fe087ce1 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-8cf8af2cc5.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-8cf8af2cc5.md · Video: p5js-8cf8af2cc5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-da62a0a467.html b/ProjectIntakeTower/explainers/web/p5js-da62a0a467.html new file mode 100644 index 0000000000000000000000000000000000000000..e5166a1ed3b048aecb66be38703ed8c7b98e2c12 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-da62a0a467.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/fixer/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-da62a0a467.md · Video: p5js-da62a0a467.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-e3537342fc.html b/ProjectIntakeTower/explainers/web/p5js-e3537342fc.html new file mode 100644 index 0000000000000000000000000000000000000000..ba2af6ab40dc1a3e6647d39226744107414b7345 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-e3537342fc.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/dlm/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-e3537342fc.md · Video: p5js-e3537342fc.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/p5js-f0deb56576.html b/ProjectIntakeTower/explainers/web/p5js-f0deb56576.html new file mode 100644 index 0000000000000000000000000000000000000000..b41b94ae06ece704321b686c7417bb9c58307b6e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/p5js-f0deb56576.html @@ -0,0 +1,6 @@ +p5js — Visual Explainer

ProjectIntakeTower Visual Explainer

p5js

/home/smlflg/.hermes/profiles/smk/skills/creative/p5js

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

p5.js Skill Production pipeline for interactive and generative visual art using [p5.js](https://p5js.org/).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 17 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 17 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:83 — 4. **PREVIEW** — Open in browser, verify visual quality. Test at target resolution. Check performance
  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:169 — For **interactive generative art** (seed exploration, parameter tuning): start from `templates/viewer.html`. Read the template first, keep the fixed sections (seed nav, actions), r
  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:255 — - Open HTML file directly in browser — no server needed for basic sketches
  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:487 — 2. **Open in browser** — `open sketch.html` (macOS) or `xdg-open sketch.html` (Linux)
  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:488 — 3. **Local assets** (fonts, images) require a server: `python3 -m http.server 8080` in the project directory, then open `http://localhost:8080/sketch.html`
  • /home/smlflg/.hermes/profiles/smk/skills/creative/p5js/SKILL.md:521 — | `templates/viewer.html` | Interactive viewer template: seed navigation (prev/next/random/jump), parameter sliders, download PNG, responsive canvas. Start from this for explorable
+

Storyboard: p5js-f0deb56576.md · Video: p5js-f0deb56576.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/paperclip-afd783b677.html b/ProjectIntakeTower/explainers/web/paperclip-afd783b677.html new file mode 100644 index 0000000000000000000000000000000000000000..d299a4bd063abae15bf3049d1c076bd1f540ac85 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/paperclip-afd783b677.html @@ -0,0 +1,6 @@ +paperclip — Visual Explainer

ProjectIntakeTower Visual Explainer

paperclip

/home/smlflg/Projekte/LuckSurface/paperclip

Tech: docs/notes · Score: 24 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Paperclip Paperclip is the output module of Samuel.SYSTEM.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 9 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 9 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/LuckSurface/paperclip/templates/clip.md:32 — ## Next Step
  • /home/smlflg/Projekte/LuckSurface/paperclip/templates/clip.md:34 — <One concrete next step.>
  • /home/smlflg/Projekte/LuckSurface/paperclip/outbox/draft-frontier-llm-harness-build.md:32 — ## Next Step
  • /home/smlflg/Projekte/LuckSurface/paperclip/outbox/draft-frontier-llm-harness-build.md:34 — Pull one short screen capture or still from the runtime switch and difference map into the next public clip so the proof reads instantly in feeds.
  • /home/smlflg/Projekte/LuckSurface/paperclip/outbox/draft-sidecar-ng-build.md:17 — - Metric / result: 97.3% accuracy (36/37), 148/148 tests pass, fail-open hook design
  • /home/smlflg/Projekte/LuckSurface/paperclip/outbox/draft-sidecar-ng-build.md:32 — ## Next Step
+

Storyboard: paperclip-afd783b677.md · Video: paperclip-afd783b677.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/passthrough-c6a263ff3d.html b/ProjectIntakeTower/explainers/web/passthrough-c6a263ff3d.html new file mode 100644 index 0000000000000000000000000000000000000000..4a527e8d8d02e5ca87b066beed8abbd3563f74a2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/passthrough-c6a263ff3d.html @@ -0,0 +1,6 @@ +passthrough — Visual Explainer

ProjectIntakeTower Visual Explainer

passthrough

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/passthrough

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

This makes it easier to pass through requests to the LLM APIs.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/passthrough/main.py:251 — # [TODO: Refactor to bedrockpassthroughconfig] need to encode the id of application-inference-profile for bedrock
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/passthrough/main.py:285 — ## SWAP MODEL IN JSON BODY [TODO: REFACTOR TO A provider_config.transform_request method]
+

Storyboard: passthrough-c6a263ff3d.md · Video: passthrough-c6a263ff3d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/path_c_builder-784223f199.html b/ProjectIntakeTower/explainers/web/path_c_builder-784223f199.html new file mode 100644 index 0000000000000000000000000000000000000000..b388b252684bcb5d51a57cfcfb5c12be9e2c71fb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/path_c_builder-784223f199.html @@ -0,0 +1,6 @@ +path_c_builder — Visual Explainer

ProjectIntakeTower Visual Explainer

path_c_builder

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/path_c_builder

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: path_c_builder-784223f199.md · Video: path_c_builder-784223f199.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/path_c_hermes-5d63d83b11.html b/ProjectIntakeTower/explainers/web/path_c_hermes-5d63d83b11.html new file mode 100644 index 0000000000000000000000000000000000000000..ebef30d60b9d04edb51a7e15fc04b72b06fff560 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/path_c_hermes-5d63d83b11.html @@ -0,0 +1,6 @@ +path_c_hermes — Visual Explainer

ProjectIntakeTower Visual Explainer

path_c_hermes

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/path_c_hermes

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: path_c_hermes-5d63d83b11.md · Video: path_c_hermes-5d63d83b11.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/path_c_research-829eb54370.html b/ProjectIntakeTower/explainers/web/path_c_research-829eb54370.html new file mode 100644 index 0000000000000000000000000000000000000000..59168fa44511f260df124d8a914915fa0edd433b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/path_c_research-829eb54370.html @@ -0,0 +1,6 @@ +path_c_research — Visual Explainer

ProjectIntakeTower Visual Explainer

path_c_research

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/path_c_research

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: path_c_research-829eb54370.md · Video: path_c_research-829eb54370.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/path_gap_deploy_learn-4e29cab738.html b/ProjectIntakeTower/explainers/web/path_gap_deploy_learn-4e29cab738.html new file mode 100644 index 0000000000000000000000000000000000000000..7ccbfee505538986410408298878ccfa38ff973d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/path_gap_deploy_learn-4e29cab738.html @@ -0,0 +1,6 @@ +path_gap_deploy_learn — Visual Explainer

ProjectIntakeTower Visual Explainer

path_gap_deploy_learn

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/path_gap_deploy_learn

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: path_gap_deploy_learn-4e29cab738.md · Video: path_gap_deploy_learn-4e29cab738.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/peer_builder-8159f475c0.html b/ProjectIntakeTower/explainers/web/peer_builder-8159f475c0.html new file mode 100644 index 0000000000000000000000000000000000000000..a33d6768f6cf3aadfc8adb99a371632f373cf893 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/peer_builder-8159f475c0.html @@ -0,0 +1,6 @@ +peer_builder — Visual Explainer

ProjectIntakeTower Visual Explainer

peer_builder

/home/smlflg/Projekte/UEBER_AGENT/bau/B_lite/peer_builder

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: peer_builder-8159f475c0.md · Video: peer_builder-8159f475c0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/peer_private-657c4b3b22.html b/ProjectIntakeTower/explainers/web/peer_private-657c4b3b22.html new file mode 100644 index 0000000000000000000000000000000000000000..5e97f1e7e5adc02b61b914b8d1f32f5c83639971 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/peer_private-657c4b3b22.html @@ -0,0 +1,6 @@ +peer_private — Visual Explainer

ProjectIntakeTower Visual Explainer

peer_private

/home/smlflg/Projekte/UEBER_AGENT/bau/B_lite/peer_private

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: peer_private-657c4b3b22.md · Video: peer_private-657c4b3b22.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/peer_research-d4278dcbc9.html b/ProjectIntakeTower/explainers/web/peer_research-d4278dcbc9.html new file mode 100644 index 0000000000000000000000000000000000000000..88844f600c082fa279e7f2a13b086690254cdb59 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/peer_research-d4278dcbc9.html @@ -0,0 +1,6 @@ +peer_research — Visual Explainer

ProjectIntakeTower Visual Explainer

peer_research

/home/smlflg/Projekte/UEBER_AGENT/bau/B_lite/peer_research

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: peer_research-d4278dcbc9.md · Video: peer_research-d4278dcbc9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/peer_router-a0edcc6393.html b/ProjectIntakeTower/explainers/web/peer_router-a0edcc6393.html new file mode 100644 index 0000000000000000000000000000000000000000..10658a12b255a7c715790d011a825980800f8327 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/peer_router-a0edcc6393.html @@ -0,0 +1,6 @@ +peer_router — Visual Explainer

ProjectIntakeTower Visual Explainer

peer_router

/home/smlflg/Projekte/UEBER_AGENT/bau/B_lite/peer_router

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: peer_router-a0edcc6393.md · Video: peer_router-a0edcc6393.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/perplexity-7999448096.html b/ProjectIntakeTower/explainers/web/perplexity-7999448096.html new file mode 100644 index 0000000000000000000000000000000000000000..6950fba684b4bc83b16702200165ccca93e29c80 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/perplexity-7999448096.html @@ -0,0 +1,6 @@ +Perplexity — Visual Explainer

ProjectIntakeTower Visual Explainer

Perplexity

/home/smlflg/Projekte/Perplexity

Tech: docker, python · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Local Answer Engine API-first Perplexity-style answer engine: search, extract, rank, synthesize, cite.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Perplexity/README.md:13 — Open `http://127.0.0.1:8000/docs`.
+

Storyboard: perplexity-7999448096.md · Video: perplexity-7999448096.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/personalchatssafe-6654f60d81.html b/ProjectIntakeTower/explainers/web/personalchatssafe-6654f60d81.html new file mode 100644 index 0000000000000000000000000000000000000000..5dfa263fe521dd670337de4773c17a633c8b81eb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/personalchatssafe-6654f60d81.html @@ -0,0 +1,6 @@ +PersonalChatsSafe! — Visual Explainer

ProjectIntakeTower Visual Explainer

PersonalChatsSafe!

/home/smlflg/Projekte/PersonalChatsSafe!

Tech: unknown · Score: 17 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 34 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 34 TODO/FIXME/WIP hints
  • unclear purpose

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/s.js:23 — !function(){"use strict";function e(t){return e="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(e){return typeof e}:function(e){return e&&"function"==typeof Sy
  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/s.js:25 — var r,o,i="function"==typeof Symbol?Symbol:{},a=i.iterator||"@@iterator",u=i.toStringTag||"@@toStringTag";function c(e,n,i,a){var u=n&&n.prototype instanceof f?n:f,c=Object.create(
  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/s.js:56 — **/We.d(He,{A:function(){return $e},k:function(){return Ve}});var Ge=function(e,t,n,r){return new(n||(n=Promise))((function(t,o){function i(e){try{u(r.next(e))}catch(e){o(e)}}funct
  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/lupk8zyo:1 — !function(){var e={76141:function(e){e.exports={source_map:"hidden-source-map",api_base:"https://api-iam.intercom.io",telemetry_base:"https://api-iam.intercom.io",public_path:"http
  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/analytics.min.js:1 — !function(){var t,e,n,r,i={8971:function(t,e,n){"use strict";var r=this&&this.__importDefault||function(t){return t&&t.__esModule?t:{default:t}};Object.defineProperty(e,"__esModule
  • /home/smlflg/Projekte/PersonalChatsSafe!/Drei wichtigste Dinge in meinem Leben - Claude_files/468742119653388:20 — (function(e,t,n,r){var o={exports:{}},a=o.exports;(function(){var a=e.fbq;if(a.execStart=e.performance&&e.performance.now&&e.performance.now(),!(function(){var t=e.postMessage||fun
+

Storyboard: personalchatssafe-6654f60d81.md · Video: personalchatssafe-6654f60d81.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/personalpromptboost-5c607caab0.html b/ProjectIntakeTower/explainers/web/personalpromptboost-5c607caab0.html new file mode 100644 index 0000000000000000000000000000000000000000..7307977f56d918810a9574d2720ef795788704ca --- /dev/null +++ b/ProjectIntakeTower/explainers/web/personalpromptboost-5c607caab0.html @@ -0,0 +1,6 @@ +personalPromptBoost — Visual Explainer

ProjectIntakeTower Visual Explainer

personalPromptBoost

/home/smlflg/Projekte/PromptBoost/personalPromptBoost

Tech: python · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

PromptBoost v0.1.1 Local prompt compiler/eval logger for personal prompt work.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/README.md:15 — Open `http://127.0.0.1:8000`.
  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/promptboost/agentic.py:61 — "open",
  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/promptboost/pipeline.py:122 — "open",
  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/promptboost/pipeline.py:255 — "review",
  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/promptboost/pipeline.py:398 — _bullet_block("Open questions", draft.get("open_questions") or ["No open questions were identified by the LLM draft."]),
  • /home/smlflg/Projekte/PromptBoost/personalPromptBoost/promptboost/pipeline.py:455 — findings.append("No-new-facts guard requires review before use.")
+

Storyboard: personalpromptboost-5c607caab0.md · Video: personalpromptboost-5c607caab0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phoenix-3dd87e38ff.html b/ProjectIntakeTower/explainers/web/phoenix-3dd87e38ff.html new file mode 100644 index 0000000000000000000000000000000000000000..db5a560187823cb23866fa62b8293cc1b5d4031c --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phoenix-3dd87e38ff.html @@ -0,0 +1,6 @@ +phoenix — Visual Explainer

ProjectIntakeTower Visual Explainer

phoenix

/home/smlflg/Projekte/symphony/elixir/deps/phoenix

Tech: node · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

<picture> <source media="(prefers-color-scheme: dark)" srcset="./priv/static/phoenix-orange.png" /> <source media="(prefers-color-scheme: light)" srcset="./priv/static/phoenix.png" /> <img src="./priv/static/phoenix.png"

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:34 — ### JavaScritp Client Bug Fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:35 — - Fix bug reconnecting connections when close was gracefully initiated by server
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:47 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:53 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:72 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix/CHANGELOG.md:77 — ### Bug fixes
+

Storyboard: phoenix-3dd87e38ff.md · Video: phoenix-3dd87e38ff.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phoenix_html-ca6e891090.html b/ProjectIntakeTower/explainers/web/phoenix_html-ca6e891090.html new file mode 100644 index 0000000000000000000000000000000000000000..7753f7c9c5c3635f98136233fdac4415f094413f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phoenix_html-ca6e891090.html @@ -0,0 +1,6 @@ +phoenix_html — Visual Explainer

ProjectIntakeTower Visual Explainer

phoenix_html

/home/smlflg/Projekte/symphony/elixir/deps/phoenix_html

Tech: node · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Phoenix.HTML Building blocks for working with HTML in Phoenix.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 35 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 35 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:11 — * Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:26 — * Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:62 — * Bug fix
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:73 — * Bug fix
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:76 — * Fix a bug where nil/false/true attributes in `aria`/`data`/`phx` would emit empty or literal values, such as `"true"` and `"false"`. This release aligns them with all other attri
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_html/CHANGELOG.md:90 — * Bug fix
+

Storyboard: phoenix_html-ca6e891090.md · Video: phoenix_html-ca6e891090.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phoenix_live_view-ad0583df44.html b/ProjectIntakeTower/explainers/web/phoenix_live_view-ad0583df44.html new file mode 100644 index 0000000000000000000000000000000000000000..f274e412af34d4d10fdf97563ee826dc2dd56e06 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phoenix_live_view-ad0583df44.html @@ -0,0 +1,6 @@ +phoenix_live_view — Visual Explainer

ProjectIntakeTower Visual Explainer

phoenix_live_view

/home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view

Tech: node · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Phoenix LiveView Phoenix LiveView enables rich, real-time user experiences with server-rendered HTML.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/README.md:75 — * [Bloom](https://github.com/chrisgreg/bloom): The opinionated, open-source extension to Phoenix Core Components
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/CHANGELOG.md:236 — Sometimes it is useful to prevent some attributes from being patched by LiveView. One example where this frequently came up is when using a native `<dialog>` or `<details>` element
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/CHANGELOG.md:239 — <details phx-mounted={JS.ignore_attributes(["open"])}>
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/CHANGELOG.md:272 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/CHANGELOG.md:279 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_live_view/CHANGELOG.md:291 — ### Bug fixes
+

Storyboard: phoenix_live_view-ad0583df44.md · Video: phoenix_live_view-ad0583df44.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phoenix_pubsub-e679e6e552.html b/ProjectIntakeTower/explainers/web/phoenix_pubsub-e679e6e552.html new file mode 100644 index 0000000000000000000000000000000000000000..464662134258c477e97031920f8f9c9a922d2f30 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phoenix_pubsub-e679e6e552.html @@ -0,0 +1,6 @@ +phoenix_pubsub — Visual Explainer

ProjectIntakeTower Visual Explainer

phoenix_pubsub

/home/smlflg/Projekte/symphony/elixir/deps/phoenix_pubsub

Tech: docs/notes · Score: 12 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Phoenix.PubSub > Distributed PubSub and Presence platform for the Phoenix Framework Usage Add `phoenix_pubsub` to your list of dependencies in `mix.exs`: ```elixir def deps do [{:phoenix_pubsub, "~> 2.0"}] end

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 3 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_pubsub/CHANGELOG.md:11 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_pubsub/CHANGELOG.md:21 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/phoenix_pubsub/CHANGELOG.md:26 — ### Bug fixes
+

Storyboard: phoenix_pubsub-e679e6e552.md · Video: phoenix_pubsub-e679e6e552.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phoenix_template-737117ad66.html b/ProjectIntakeTower/explainers/web/phoenix_template-737117ad66.html new file mode 100644 index 0000000000000000000000000000000000000000..411fc1634eb4788991978a54812039a08d475609 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phoenix_template-737117ad66.html @@ -0,0 +1,6 @@ +phoenix_template — Visual Explainer

ProjectIntakeTower Visual Explainer

phoenix_template

/home/smlflg/Projekte/symphony/elixir/deps/phoenix_template

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Phoenix.Template Templates are markup languages that are compiled to Elixir code.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: phoenix_template-737117ad66.md · Video: phoenix_template-737117ad66.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/phx.gen.auth-0708615926.html b/ProjectIntakeTower/explainers/web/phx.gen.auth-0708615926.html new file mode 100644 index 0000000000000000000000000000000000000000..8ad4863468a657f3624d3ad367d3cfb5061c0612 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/phx.gen.auth-0708615926.html @@ -0,0 +1,6 @@ +phx.gen.auth — Visual Explainer

ProjectIntakeTower Visual Explainer

phx.gen.auth

/home/smlflg/Projekte/symphony/elixir/deps/phoenix/priv/templates/phx.gen.auth

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: phx.gen.auth-0708615926.md · Video: phx.gen.auth-0708615926.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/plan-gen-eval-0c28947b2a.html b/ProjectIntakeTower/explainers/web/plan-gen-eval-0c28947b2a.html new file mode 100644 index 0000000000000000000000000000000000000000..4f94e475bdd07cb96ccc874cf2f70ed2224b204d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/plan-gen-eval-0c28947b2a.html @@ -0,0 +1,6 @@ +plan-gen-eval — Visual Explainer

ProjectIntakeTower Visual Explainer

plan-gen-eval

/home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval

Tech: agent, node, typescript · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 33 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 33 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/plan-gen-eval/clean-state-checklist.md:15 — - [ ] No React imports in services or main process
+

Storyboard: plan-gen-eval-0c28947b2a.md · Video: plan-gen-eval-0c28947b2a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/plug-e0003286cf.html b/ProjectIntakeTower/explainers/web/plug-e0003286cf.html new file mode 100644 index 0000000000000000000000000000000000000000..28bdc6018ccf18ca144a3e2ba52471dbcbe72113 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/plug-e0003286cf.html @@ -0,0 +1,6 @@ +plug — Visual Explainer

ProjectIntakeTower Visual Explainer

plug

/home/smlflg/Projekte/symphony/elixir/deps/plug

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Plug Plug is: 1.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 29 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 29 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/plug/README.md:112 — sock.addEventListener("open", () => sock.send("ping"))
  • /home/smlflg/Projekte/symphony/elixir/deps/plug/README.md:148 — supervision tree. See the [Supervised handlers](#supervised-handlers) section next.
  • /home/smlflg/Projekte/symphony/elixir/deps/plug/README.md:337 — Use the [issue tracker][issues] for bug reports or feature requests. Open a [pull request][pulls] when you are ready to contribute. When submitting a pull request you should not up
  • /home/smlflg/Projekte/symphony/elixir/deps/plug/README.md:347 — | v1.15 | Bug fixes |
  • /home/smlflg/Projekte/symphony/elixir/deps/plug/CHANGELOG.md:5 — ### Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/plug/CHANGELOG.md:59 — ### Bug fixes
+

Storyboard: plug-e0003286cf.md · Video: plug-e0003286cf.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/plug_crypto-11ce53b944.html b/ProjectIntakeTower/explainers/web/plug_crypto-11ce53b944.html new file mode 100644 index 0000000000000000000000000000000000000000..a8b7e58dc587aff51aa83e06630cd04b2c36e3ff --- /dev/null +++ b/ProjectIntakeTower/explainers/web/plug_crypto-11ce53b944.html @@ -0,0 +1,6 @@ +plug_crypto — Visual Explainer

ProjectIntakeTower Visual Explainer

plug_crypto

/home/smlflg/Projekte/symphony/elixir/deps/plug_crypto

Tech: docs/notes · Score: 12 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Plug.Crypto Crypto-related functionality for web applications, used by [Plug](https://github.com/elixir-plug/plug).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 3 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/plug_crypto/README.md:24 — - Use the [issue tracker](https://github.com/elixir-plug/plug_crypto/issues) for bug reports or feature requests.
  • /home/smlflg/Projekte/symphony/elixir/deps/plug_crypto/README.md:25 — - Open a [pull request](https://github.com/elixir-plug/plug_crypto/pulls) when you are ready to contribute.
  • /home/smlflg/Projekte/symphony/elixir/deps/plug_crypto/CHANGELOG.md:40 — * Fixed a bug that allowed to sign and encrypt stuff with `nil` secret key base and salt.
+

Storyboard: plug_crypto-11ce53b944.md · Video: plug_crypto-11ce53b944.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/portable-c241dbb668.html b/ProjectIntakeTower/explainers/web/portable-c241dbb668.html new file mode 100644 index 0000000000000000000000000000000000000000..7b589984961b7e26fe74881b8630d74aa8954c92 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/portable-c241dbb668.html @@ -0,0 +1,6 @@ +portable — Visual Explainer

ProjectIntakeTower Visual Explainer

portable

/home/smlflg/Projekte/MyAIGame/portable

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Portable Setup > One source, three targets.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/MyAIGame/portable/deploy.sh:220 — if python3 -c "import json; json.load(open('$claude_dir/settings.json'))" 2>/dev/null; then
  • /home/smlflg/Projekte/MyAIGame/portable/deploy.sh:257 — if python3 -c "import json; json.load(open('$oc_dir/opencode.json'))" 2>/dev/null; then
  • /home/smlflg/Projekte/MyAIGame/portable/deploy.sh:366 — log_warn "Review and merge manually: diff $claude_dir/settings.json $settings_src"
  • /home/smlflg/Projekte/MyAIGame/portable/README_UPDATE.md:94 — - **Git workflows** -- setup-git, review, commit patterns
  • /home/smlflg/Projekte/MyAIGame/portable/README_UPDATE.md:120 — | Tier | Role | Claude/Anthropic | OpenAI | Open Source |
  • /home/smlflg/Projekte/MyAIGame/portable/README_UPDATE.md:137 — Execution chef, chef-lite, chef-async, test, review, debug-loop (~$3)
+

Storyboard: portable-c241dbb668.md · Video: portable-c241dbb668.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/portable-io-f33a020e41.html b/ProjectIntakeTower/explainers/web/portable-io-f33a020e41.html new file mode 100644 index 0000000000000000000000000000000000000000..294cd56360c6bab3647a7a16e6107fadd0eeae1a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/portable-io-f33a020e41.html @@ -0,0 +1,6 @@ +portable-io — Visual Explainer

ProjectIntakeTower Visual Explainer

portable-io

/home/smlflg/Projekte/Harness_swap/packages/portable-io

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: portable-io-f33a020e41.md · Video: portable-io-f33a020e41.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/portfoliotimeline-74850fb9b9.html b/ProjectIntakeTower/explainers/web/portfoliotimeline-74850fb9b9.html new file mode 100644 index 0000000000000000000000000000000000000000..f55eaf5ae2308780d2feca39189012a3d22ffc0b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/portfoliotimeline-74850fb9b9.html @@ -0,0 +1,6 @@ +PortfolioTimeline — Visual Explainer

ProjectIntakeTower Visual Explainer

PortfolioTimeline

/home/smlflg/Projekte/PortfolioTimeline

Tech: unknown · Score: 52 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 29 TODO/FIXME-Hinweise, uncommitted changes, 7 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 29 TODO/FIXME/WIP hints
  • plans/backlogs found
  • unclear purpose

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PortfolioTimeline/generate_screenshots.py:18 — {"path": "/home/smlflg/.agent/diagrams/claudecodepanel-deep-review.html", "slug": "diagrams--claudecodepanel-deep-review"},
  • /home/smlflg/Projekte/PortfolioTimeline/generate_screenshots.py:42 — {"path": "/home/smlflg/.agent/diagrams/analyses/agentide-v03-review-report.html", "slug": "diagrams--agentide-v03-review-report"},
  • /home/smlflg/Projekte/PortfolioTimeline/generate_screenshots.py:47 — {"path": "/home/smlflg/.agent/diagrams/analyses/minimax-bug-meta-analyse.html", "slug": "diagrams--minimax-bug-meta-analyse"},
  • /home/smlflg/Projekte/PortfolioTimeline/cms_md_parser.py:41 — with open(DATA_FILE, "r", encoding="utf-8") as f:
  • /home/smlflg/Projekte/PortfolioTimeline/cms_md_parser.py:48 — with open(DATA_FILE, "r", encoding="utf-8") as f:
  • /home/smlflg/Projekte/PortfolioTimeline/cms_md_parser.py:56 — with open(DATA_FILE, "w", encoding="utf-8") as f:
+

Storyboard: portfoliotimeline-74850fb9b9.md · Video: portfoliotimeline-74850fb9b9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/prior-art-2026-04-10-9d028b3600.html b/ProjectIntakeTower/explainers/web/prior-art-2026-04-10-9d028b3600.html new file mode 100644 index 0000000000000000000000000000000000000000..fe2b19d63076c27692b9775d8095ae45ab4066a2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/prior-art-2026-04-10-9d028b3600.html @@ -0,0 +1,6 @@ +prior-art-2026-04-10 — Visual Explainer

ProjectIntakeTower Visual Explainer

prior-art-2026-04-10

/home/smlflg/Projekte/prior-art-2026-04-10

Tech: docs/notes · Score: 20 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Prior Art Snapshot - 2026-04-10 Created: 2026-04-10T14:58:10+02:00 This repository is a dated snapshot of knowledge, patterns, architectures, lessons, and project lines that already existed before the start of any later

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 3 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/prior-art-2026-04-10/README.md:67 — 1. create and review files locally
  • /home/smlflg/Projekte/prior-art-2026-04-10/projects/SIDECAR_PRIOR_ART_2026-04-10.md:25 — - fail-open behavior so the host assistant continues even if the sidecar layer fails
  • /home/smlflg/Projekte/prior-art-2026-04-10/projects/OBSERVER_EVOLVE_PRIOR_ART_2026-04-10.md:26 — - message protocols between agents benefit from explicit fields such as intent, payload, confidence, verification status, and next action
+

Storyboard: prior-art-2026-04-10-9d028b3600.md · Video: prior-art-2026-04-10-9d028b3600.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/profile-ed7357a4ca.html b/ProjectIntakeTower/explainers/web/profile-ed7357a4ca.html new file mode 100644 index 0000000000000000000000000000000000000000..2e5927f3424c6d673e67dc6d9d832dc205d9aaf5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/profile-ed7357a4ca.html @@ -0,0 +1,6 @@ +profile — Visual Explainer

ProjectIntakeTower Visual Explainer

profile

/home/smlflg/Projekte/Harness_swap/packages/profile

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: profile-ed7357a4ca.md · Video: profile-ed7357a4ca.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-01-04af3e8b57.html b/ProjectIntakeTower/explainers/web/project-01-04af3e8b57.html new file mode 100644 index 0000000000000000000000000000000000000000..8782df9f2a6d762a7488eeb75937b6940d6ee9fa --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-01-04af3e8b57.html @@ -0,0 +1,6 @@ +project-01 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-01

/home/smlflg/Projekte/learn-harness-engineering/projects/project-01

Tech: docs/notes · Score: 18 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 01: Baseline vs Minimal Harness 比较弱 harness(仅靠 prompt)和显式 harness(规则文件 + 验证机制)对 AI 编码代理任务完成率的影响。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——只有一个模糊的 `task-prompt.md`,没有 AGENTS.md、没有 feature_list.json。

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 5 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 5 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/claude-progress.md:27 — **Next session**: Proceed to Project 02 to add import, detail view, and persistence features.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/starter/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
+

Storyboard: project-01-04af3e8b57.md · Video: project-01-04af3e8b57.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-02-9458e05232.html b/ProjectIntakeTower/explainers/web/project-02-9458e05232.html new file mode 100644 index 0000000000000000000000000000000000000000..4cff6d0bcc6ed22115ebfaf8495575871ed4c84d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-02-9458e05232.html @@ -0,0 +1,6 @@ +project-02 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-02

/home/smlflg/Projekte/learn-harness-engineering/projects/project-02

Tech: docs/notes · Score: 17 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 02: Agent-Readable Workspace 演示仓库可读性和显式连续性产物如何减少跨会话开发中的上下文丢失。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——基于 P1 solution 的代码,新增文档导入、详情视图、持久化功能待实现。harness 较弱:AGENTS.md 简陋,没有 session-handoff。 | | `solut

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, 3 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/solution/session-handoff.md:50 — ### Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/starter/src/renderer/components/DocumentDetail.tsx:18 — // TODO: Load document content for viewing -- not yet implemented
+

Storyboard: project-02-9458e05232.md · Video: project-02-9458e05232.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-03-9eacf09d55.html b/ProjectIntakeTower/explainers/web/project-03-9eacf09d55.html new file mode 100644 index 0000000000000000000000000000000000000000..53fb1f2b33175b15d2b4486a7bfb3bbccbf911c4 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-03-9eacf09d55.html @@ -0,0 +1,6 @@ +project-03 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-03

/home/smlflg/Projekte/learn-harness-engineering/projects/project-03

Tech: docs/notes · Score: 19 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 03: Scope Control and Grounded Verification 评估显式范围控制和验证门控是否能提高交付准确性。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——基于 P2 solution,新增文档分块、元数据提取、索引状态、基础问答功能待实现。没有一次一个功能的策略约束。 | | `solution/` | **参考实现**——所

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 5 TODO/FIXME-Hinweise, 3 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 5 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/session-handoff.md:41 — - The one-feature-at-a-time policy from AGENTS.md was followed strictly: each feature was implemented, verified, and recorded before moving to the next.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/session-handoff.md:66 — ### Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/AGENTS.md:24 — 6. **Only then** move to the next feature.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
+

Storyboard: project-03-9eacf09d55.md · Video: project-03-9eacf09d55.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-04-6c931dfe71.html b/ProjectIntakeTower/explainers/web/project-04-6c931dfe71.html new file mode 100644 index 0000000000000000000000000000000000000000..c666abf56e4d8a828b9e35cdc85f74b9a30030cc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-04-6c931dfe71.html @@ -0,0 +1,6 @@ +project-04 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-04

/home/smlflg/Projekte/learn-harness-engineering/projects/project-04

Tech: docs/notes · Score: 33 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 04: Runtime Observability and Structural Control 引入运行时可观测性和结构化边界检查,同时调试一个植入的运行时缺陷。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——基于 P3 solution,新增日志、结构化边界功能待实现。`IndexingService` 中植入了一个隐蔽 bug:超过 1000 字符的

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 30 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 30 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/README.md:9 — | `starter/` | **起点**——基于 P3 solution,新增日志、结构化边界功能待实现。`IndexingService` 中植入了一个隐蔽 bug:超过 1000 字符的文件会产生空分块。没有架构检查脚本。 |
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/README.md:10 — | `solution/` | **参考实现**——结构化日志模块、架构边界检查脚本、植入 bug 已修复。 |
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/README.md:17 — # 1. 观察 agent 能否通过日志定位 bug
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
+

Storyboard: project-04-6c931dfe71.md · Video: project-04-6c931dfe71.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-05-8cd6089d80.html b/ProjectIntakeTower/explainers/web/project-05-8cd6089d80.html new file mode 100644 index 0000000000000000000000000000000000000000..c6a1fe9d23f42c5506784716dc33c0ad0754cdba --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-05-8cd6089d80.html @@ -0,0 +1,6 @@ +project-05 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-05

/home/smlflg/Projekte/learn-harness-engineering/projects/project-05

Tech: docs/notes · Score: 32 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 05: Evaluator Loops and Three-Role Upgrades 测量角色分离(单角色 / 生成+评估 / 计划+生成+评估)如何改变实现质量。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——基于 P4 solution,新增多轮问答历史功能待实现。 | | `solution/single-role/` | **变体 A**——一个

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/gen-eval/clean-state-checklist.md:15 — - [ ] No React imports in services or main process
+

Storyboard: project-05-8cd6089d80.md · Video: project-05-8cd6089d80.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/project-06-90c6b73736.html b/ProjectIntakeTower/explainers/web/project-06-90c6b73736.html new file mode 100644 index 0000000000000000000000000000000000000000..833c8a1f13cdff57c81e9456e570289801389978 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/project-06-90c6b73736.html @@ -0,0 +1,6 @@ +project-06 — Visual Explainer

ProjectIntakeTower Visual Explainer

project-06

/home/smlflg/Projekte/learn-harness-engineering/projects/project-06

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Project 06: Runtime Observability and Debugging (Capstone) 课程毕业项目:构建并基准测试完整的 harness,执行清理循环验证质量可维护性。 目录说明 | 目录 | 含义 | |------|------| | `starter/` | **起点**——完整的产品代码,但 harness 被刻意削弱(只有基础 AGENTS.md,没有 feature_list.json、ses

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/claude-progress.md:40 — **Next session**: No remaining features. Project 06 is complete.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:9 — - [ ] No TypeScript warnings about unused variables or imports
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code (`src/renderer/`)
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code (`src/services/`)
+

Storyboard: project-06-90c6b73736.md · Video: project-06-90c6b73736.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/projectdashboard-31c8de4fc8.html b/ProjectIntakeTower/explainers/web/projectdashboard-31c8de4fc8.html new file mode 100644 index 0000000000000000000000000000000000000000..3dc920a979b4defffca684cb7a75471ebc898fd5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/projectdashboard-31c8de4fc8.html @@ -0,0 +1,6 @@ +ProjectDashboard — Visual Explainer

ProjectIntakeTower Visual Explainer

ProjectDashboard

/home/smlflg/Projekte/ProjectDashboard

Tech: python · Score: 40 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ProjectDashboard Live dashboard that auto-scans all projects in `~/Projekte/` and displays them as a web overview.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 22 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 22 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/ProjectDashboard/models.py:70 — with open(scan_path) as f:
  • /home/smlflg/Projekte/ProjectDashboard/main.py:20 — with open("/tmp/project-dashboard-scan.json", "w") as f:
  • /home/smlflg/Projekte/ProjectDashboard/main.py:68 — with open("/tmp/project-dashboard-scan.json", "w") as f:
  • /home/smlflg/Projekte/ProjectDashboard/scanner.py:32 — total += sum(1 for _ in open(os.path.join(root, f), errors="ignore"))
  • /home/smlflg/Projekte/ProjectDashboard/scanner.py:122 — # Count numbered items without checkboxes as open
  • /home/smlflg/Projekte/ProjectDashboard/scanner.py:158 — return json.load(open(override_path))
+

Storyboard: projectdashboard-31c8de4fc8.md · Video: projectdashboard-31c8de4fc8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/projectintaketower-25667b42ac.html b/ProjectIntakeTower/explainers/web/projectintaketower-25667b42ac.html new file mode 100644 index 0000000000000000000000000000000000000000..38c32cda9d3fab5d893bd5968036c900a02b49a8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/projectintaketower-25667b42ac.html @@ -0,0 +1,6 @@ +ProjectIntakeTower — Visual Explainer

ProjectIntakeTower Visual Explainer

ProjectIntakeTower

/home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ProjectIntakeTower ProjectIntakeTower is a local, read-only intake harness for Samuel's machine.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:35 — > Can the next token produce an artifact that is useful tomorrow?
  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:42 — - review report
  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:70 — - review of produced artifacts
  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:85 — 7. Generate pending review-only job contracts.
  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:93 — - open GitHub issues automatically
  • /home/smlflg/Projekte/AgentProjectMinenraeumer/ProjectIntakeTower/PANIC_QUOTA_STOPLOSS.md:98 — ## Next 30-minute plan
+

Storyboard: projectintaketower-25667b42ac.md · Video: projectintaketower-25667b42ac.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/projekte-9bed6fa1d9.html b/ProjectIntakeTower/explainers/web/projekte-9bed6fa1d9.html new file mode 100644 index 0000000000000000000000000000000000000000..cf662473231f8681d0cf251c64f4e12c5667d2bd --- /dev/null +++ b/ProjectIntakeTower/explainers/web/projekte-9bed6fa1d9.html @@ -0,0 +1,6 @@ +Projekte — Visual Explainer

ProjectIntakeTower Visual Explainer

Projekte

/home/smlflg/Projekte

Tech: unknown · Score: 27 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • plans/backlogs found
  • unclear purpose

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/todo3tasks:1 — Agent "Scan projects for open todos" completed
  • /home/smlflg/Projekte/todo3tasks:19 — Woche 2: Codex (Review/Finish lernen)
  • /home/smlflg/Projekte/todo3tasks:21 — Projekt: ClaudeCodePanel Polish — Code Review + Refactoring
  • /home/smlflg/Projekte/todo3tasks:22 — - 4 konkrete Review-Suggestions liegen schon vor (sorted-Lambda, unused Parameter,
  • /home/smlflg/Projekte/todo3tasks:24 — - Warum perfekt: Codex IST ein Review/Polish-Tool — du lernst es genau in seiner
  • /home/smlflg/Projekte/todo3tasks:26 — - Was du lernst: codex review, Runbook-Modes (review vs build), Sandbox-Settings,
+

Storyboard: projekte-9bed6fa1d9.md · Video: projekte-9bed6fa1d9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/promptboost-c71f823581.html b/ProjectIntakeTower/explainers/web/promptboost-c71f823581.html new file mode 100644 index 0000000000000000000000000000000000000000..5a214ce8f4eabab7ea64474dd550127b0f5c99d1 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/promptboost-c71f823581.html @@ -0,0 +1,6 @@ +PromptBoost — Visual Explainer

ProjectIntakeTower Visual Explainer

PromptBoost

/home/smlflg/Projekte/PromptBoost

Tech: node · Score: 26 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PromptBoost/ideal:150 — * **Review-/Plan-Disziplin**
  • /home/smlflg/Projekte/PromptBoost/ideal:254 — * **Review-Disziplin**
  • /home/smlflg/Projekte/PromptBoost/ideal:373 — - After local extraction, perform explicit review passes:
  • /home/smlflg/Projekte/PromptBoost/ideal:391 — - review notes
  • /home/smlflg/Projekte/PromptBoost/ideal:404 — * Review-Phasen,
  • /home/smlflg/Projekte/PromptBoost/ideal:520 — * Plan- und Review-Disziplin
+

Storyboard: promptboost-c71f823581.md · Video: promptboost-c71f823581.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/promptgarage-0b3c0c62a5.html b/ProjectIntakeTower/explainers/web/promptgarage-0b3c0c62a5.html new file mode 100644 index 0000000000000000000000000000000000000000..da54a37e260dc9ce27cbb7452aaae58ceca405d5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/promptgarage-0b3c0c62a5.html @@ -0,0 +1,6 @@ +PromptGarage — Visual Explainer

ProjectIntakeTower Visual Explainer

PromptGarage

/home/smlflg/Projekte/PromptGarage

Tech: python · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

PromptGarage CLI tool for collecting, curating, and searching prompts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 13 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 13 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PromptGarage/prompt-launcher-voice.sh:42 — # 6. Open main fuzzel with all prompts
  • /home/smlflg/Projekte/PromptGarage/tagger.py:26 — "bug": "debugging",
  • /home/smlflg/Projekte/PromptGarage/FOR_SMLFLG.md:8 — ## Spaeter-TODO
  • /home/smlflg/Projekte/PromptGarage/importer.py:44 — with open(fpath, "r") as f:
  • /home/smlflg/Projekte/PromptGarage/importer.py:103 — with open(fpath, "r") as f:
  • /home/smlflg/Projekte/PromptGarage/importer.py:156 — with open(fpath, "r") as f:
+

Storyboard: promptgarage-0b3c0c62a5.md · Video: promptgarage-0b3c0c62a5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/promptgarageui-06119fedc7.html b/ProjectIntakeTower/explainers/web/promptgarageui-06119fedc7.html new file mode 100644 index 0000000000000000000000000000000000000000..36e1cfcbf35501b3afd81bba56c60116757703f6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/promptgarageui-06119fedc7.html @@ -0,0 +1,6 @@ +PromptGarageUI — Visual Explainer

ProjectIntakeTower Visual Explainer

PromptGarageUI

/home/smlflg/Projekte/PromptGarageUI

Tech: python · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: promptgarageui-06119fedc7.md · Video: promptgarageui-06119fedc7.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/proxy-ba82ffa05c.html b/ProjectIntakeTower/explainers/web/proxy-ba82ffa05c.html new file mode 100644 index 0000000000000000000000000000000000000000..ffcc95eae1aa9e502e682a7ff713a9dfd24a19c0 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/proxy-ba82ffa05c.html @@ -0,0 +1,6 @@ +proxy — Visual Explainer

ProjectIntakeTower Visual Explainer

proxy

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/types/proxy

Tech: docs/notes · Score: 15 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

These are file-specific types for the proxy.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/types/proxy/policy_engine/pipeline_types.py:13 — VALID_PIPELINE_ACTIONS = {"allow", "block", "next", "modify_response"}
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/types/proxy/policy_engine/pipeline_types.py:27 — description="Action when guardrail rejects: next | block | allow | modify_response",
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/types/proxy/policy_engine/pipeline_types.py:31 — description="Action when guardrail passes: next | block | allow | modify_response",
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/types/proxy/policy_engine/pipeline_types.py:35 — description="Forward modified request data (e.g., PII-masked) to next step.",
+

Storyboard: proxy-ba82ffa05c.md · Video: proxy-ba82ffa05c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/proxy-edfc3853a7.html b/ProjectIntakeTower/explainers/web/proxy-edfc3853a7.html new file mode 100644 index 0000000000000000000000000000000000000000..07ebf92c2fb932d26f6fe70c5a66995347c24bf0 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/proxy-edfc3853a7.html @@ -0,0 +1,6 @@ +proxy — Visual Explainer

ProjectIntakeTower Visual Explainer

proxy

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

litellm-proxy A local, fast, and lightweight **OpenAI-compatible server** to call 100+ LLM APIs.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/proxy_cli.py:306 — with open(os.devnull, "w") as devnull:
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/health_check.py:134 — idx, next_model = next(model_iter)
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/openapi_registry.json:19 — { "name": "create_issue", "description": "Open a new issue in a repository" },
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/openapi_registry.json:20 — { "name": "list_pull_requests", "description": "List open and merged pull requests" },
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/openapi_registry.json:21 — { "name": "create_pull_request", "description": "Open a pull request between branches" },
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/openapi_registry.json:41 — { "name": "create_issue", "description": "Create a new Jira issue or bug report" },
+

Storyboard: proxy-edfc3853a7.md · Video: proxy-edfc3853a7.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/pseudologikpyhthoncpp-4e906fdb55.html b/ProjectIntakeTower/explainers/web/pseudologikpyhthoncpp-4e906fdb55.html new file mode 100644 index 0000000000000000000000000000000000000000..bf883e829d6b1eed083f93275a7143793190d3bb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/pseudologikpyhthoncpp-4e906fdb55.html @@ -0,0 +1,6 @@ +PseudoLogikPyhthonCPP — Visual Explainer

ProjectIntakeTower Visual Explainer

PseudoLogikPyhthonCPP

/home/smlflg/Projekte/PseudoLogikPyhthonCPP

Tech: node · Score: 38 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 5 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:22 — │ │ │ /api/review │
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:149 — state: 'New' | 'Learning' | 'Review' | 'Relearning'
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:178 — POST /api/cards/:id/review — Review + FSRS-Update
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:197 — ## Review-Modus
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:213 — │ └── Review.tsx # SRS-Session
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/GLM_Solution.md:218 — │ ├── ReviewCard.tsx # 2-Spalten Review
+

Storyboard: pseudologikpyhthoncpp-4e906fdb55.md · Video: pseudologikpyhthoncpp-4e906fdb55.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/python-e97ce5d102.html b/ProjectIntakeTower/explainers/web/python-e97ce5d102.html new file mode 100644 index 0000000000000000000000000000000000000000..255ecc6ca8c71b9b6db8317f5230e80ca6f5c6bf --- /dev/null +++ b/ProjectIntakeTower/explainers/web/python-e97ce5d102.html @@ -0,0 +1,6 @@ +python — Visual Explainer

ProjectIntakeTower Visual Explainer

python

/home/smlflg/Projekte/derWolfimSchafspelz/openclaude/python

Tech: python · Score: 2 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/python/smart_router.py:333 — provider = next(
+

Storyboard: python-e97ce5d102.md · Video: python-e97ce5d102.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/realtime_api-b67b31192e.html b/ProjectIntakeTower/explainers/web/realtime_api-b67b31192e.html new file mode 100644 index 0000000000000000000000000000000000000000..0024f13ead654f404ce89215c070a2aa4e6f0c62 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/realtime_api-b67b31192e.html @@ -0,0 +1,6 @@ +realtime_api — Visual Explainer

ProjectIntakeTower Visual Explainer

realtime_api

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/realtime_api

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Abstraction / Routing logic for OpenAI's `/v1/realtime` endpoint.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: realtime_api-b67b31192e.md · Video: realtime_api-b67b31192e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/release-2db488872d.html b/ProjectIntakeTower/explainers/web/release-2db488872d.html new file mode 100644 index 0000000000000000000000000000000000000000..4a98d6fde84e9bdc950ab6ac37ec76b490d2e227 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/release-2db488872d.html @@ -0,0 +1,6 @@ +release — Visual Explainer

ProjectIntakeTower Visual Explainer

release

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release

Tech: docker, python · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

**NOTE: The release script is currently in the process of moving from Vagrant/fabric to Docker/rever.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 30 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 30 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/github_release.py:107 — with open(os.path.join('release/release-' + version, tarball), 'rb') as f:
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/github_release.py:117 — # TODO: download the files and check that they have the right sha256 sum
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/github_release.py:201 — with open(path) as f:
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/github_release.py:313 — In case of a multipage result, DOES NOT query the next page.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/github_release.py:357 — with open(token_file_expand, 'w') as f:
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/release/sha256.py:23 — with open(outdir / 'sha256.txt', 'w') as shafile:
+

Storyboard: release-2db488872d.md · Video: release-2db488872d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/repo-template-a0f4b0157d.html b/ProjectIntakeTower/explainers/web/repo-template-a0f4b0157d.html new file mode 100644 index 0000000000000000000000000000000000000000..8454fc12f4523120b5da28ea87ed3224d39334d8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/repo-template-a0f4b0157d.html @@ -0,0 +1,6 @@ +repo-template — Visual Explainer

ProjectIntakeTower Visual Explainer

repo-template

/home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template

Tech: agent · Score: 33 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 11 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 11 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/AGENTS.md:14 — 4. Read `docs/PLANS.md`, then open the active plan you are working from.
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/AGENTS.md:37 — - If you see repeated review feedback, promote it into a mechanical rule, check,
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/AGENTS.md:61 — 5. Leave the repo in a restartable state with a clear next action.
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/docs/SECURITY.md:23 — ## Dependency And Review Rules
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/docs/SECURITY.md:27 — - Repeated security review comments should become checks, not tribal knowledge.
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/openai-advanced/repo-template/docs/QUALITY_SCORE.md:32 — | Date | Harness Variant | Completion Rate | Retries | Defects Before Review | Notes |
+

Storyboard: repo-template-a0f4b0157d.md · Video: repo-template-a0f4b0157d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/repo-template-ec29134565.html b/ProjectIntakeTower/explainers/web/repo-template-ec29134565.html new file mode 100644 index 0000000000000000000000000000000000000000..a4a3409162e5a3d74da62e0512f303f68c9de2ad --- /dev/null +++ b/ProjectIntakeTower/explainers/web/repo-template-ec29134565.html @@ -0,0 +1,6 @@ +repo-template — Visual Explainer

ProjectIntakeTower Visual Explainer

repo-template

/home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/openai-advanced/repo-template

Tech: agent · Score: 19 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/openai-advanced/repo-template/AGENTS.md:33 — - 如果某类 review feedback 反复出现,把它升级成机械规则、检查或 linter,不要一直在聊天里重复解释。
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/openai-advanced/repo-template/docs/SECURITY.md:27 — - 反复出现的安全 review 评论要升级成检查,而不是变成口口相传的经验。
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/openai-advanced/repo-template/docs/QUALITY_SCORE.md:31 — | 日期 | Harness 变体 | 完成率 | 重试次数 | Review 前缺陷数 | 备注 |
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/openai-advanced/repo-template/docs/FRONTEND.md:17 — - 修复 UI bug 后,顺手补上对应验证步骤。
+

Storyboard: repo-template-ec29134565.md · Video: repo-template-ec29134565.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/req-b8e1e3a474.html b/ProjectIntakeTower/explainers/web/req-b8e1e3a474.html new file mode 100644 index 0000000000000000000000000000000000000000..8db30e3056cc3d3c7a41f84d92414b45b5042428 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/req-b8e1e3a474.html @@ -0,0 +1,6 @@ +req — Visual Explainer

ProjectIntakeTower Visual Explainer

req

/home/smlflg/Projekte/symphony/elixir/deps/req

Tech: docs/notes · Score: 16 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Req Req is a batteries-included HTTP client for Elixir.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 5 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 5 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/req/README.md:193 — # open browser window? [Yn]
  • /home/smlflg/Projekte/symphony/elixir/deps/req/CHANGELOG.md:200 — * [`put_aws_sigv4`]: Fix bug when using custom headers
  • /home/smlflg/Projekte/symphony/elixir/deps/req/CHANGELOG.md:222 — Req v0.5.0 brings testing enhancements, errors standardization, `%Req.Response.Async{}`, and more improvements and bug fixes.
  • /home/smlflg/Projekte/symphony/elixir/deps/req/CHANGELOG.md:893 — * [`put_params`]: Fix bug when params have been duplicated when retrying requeset
  • /home/smlflg/Projekte/symphony/elixir/deps/req/CHANGELOG.md:1030 — # open browser window? [Yn]
+

Storyboard: req-b8e1e3a474.md · Video: req-b8e1e3a474.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/router_a-c32e68f47c.html b/ProjectIntakeTower/explainers/web/router_a-c32e68f47c.html new file mode 100644 index 0000000000000000000000000000000000000000..fe656efd61b07a41715f26e57c9734867724af9b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/router_a-c32e68f47c.html @@ -0,0 +1,6 @@ +router_a — Visual Explainer

ProjectIntakeTower Visual Explainer

router_a

/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/router_a

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: router_a-c32e68f47c.md · Video: router_a-c32e68f47c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/runtime-routerdisziplin-d0cce9f4a3.html b/ProjectIntakeTower/explainers/web/runtime-routerdisziplin-d0cce9f4a3.html new file mode 100644 index 0000000000000000000000000000000000000000..218e9908a2669c41383be8d442c7801558a437d1 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/runtime-routerdisziplin-d0cce9f4a3.html @@ -0,0 +1,6 @@ +Runtime+RouterDisziplin — Visual Explainer

ProjectIntakeTower Visual Explainer

Runtime+RouterDisziplin

/home/smlflg/Projekte/UEBER_AGENT/Runtime+RouterDisziplin

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Runtime+RouterDisziplin Dieser Ordner ist das operative Dach fuer zwei eng gekoppelte Probleme: - Runtime-Fehler auf der Debian-VM - Router-Disziplin von `stern1` Er ersetzt keine bestehenden Quellen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: runtime-routerdisziplin-d0cce9f4a3.md · Video: runtime-routerdisziplin-d0cce9f4a3.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/samuel-3f2ebe9000.html b/ProjectIntakeTower/explainers/web/samuel-3f2ebe9000.html new file mode 100644 index 0000000000000000000000000000000000000000..9f1569ee422d2192e4ef08e8f05134a0b1988851 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/samuel-3f2ebe9000.html @@ -0,0 +1,6 @@ +samuel — Visual Explainer

ProjectIntakeTower Visual Explainer

samuel

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel

Tech: python · Score: 25 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/data/core_memory.md:38 — Denke auf Architektur-Niveau (Adapter Patterns, Fallback-Ketten, Trade-off-Matrizen). Aber Implementation bleibt lueckenhaft. 40+ Seiten ADD fuer ~700 Zeilen Code. Keeper await-Bug
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/data/fear_map.json:32 — "evidence": "Keeper await-Bug seit Monaten offen. 5 BUILD_SPECS, 0 implementiert",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/data/fear_map.json:35 — "Keeper: await-Bug ein Einzeiler, seit Monaten offen",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/data/fear_map.json:39 — "micro_offer": "Ein Keeper-Bug fixen? 15 Min."
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/tests/test_replay_parser.py:27 — "message": {"role": "user", "content": "Fix the bug"},
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/samuel/tests/test_pattern_detector.py:67 — hyperfocus = next(s for s in signals if s.pattern_type == "hyperfocus")
+

Storyboard: samuel-3f2ebe9000.md · Video: samuel-3f2ebe9000.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/samuel-474277b9a5.html b/ProjectIntakeTower/explainers/web/samuel-474277b9a5.html new file mode 100644 index 0000000000000000000000000000000000000000..a6db1cc54f881351a0b6262978f45953f2faeac4 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/samuel-474277b9a5.html @@ -0,0 +1,6 @@ +samuel — Visual Explainer

ProjectIntakeTower Visual Explainer

samuel

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel

Tech: python · Score: 25 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 28 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 28 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/data/core_memory.md:38 — Denke auf Architektur-Niveau (Adapter Patterns, Fallback-Ketten, Trade-off-Matrizen). Aber Implementation bleibt lueckenhaft. 40+ Seiten ADD fuer ~700 Zeilen Code. Keeper await-Bug
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/data/fear_map.json:32 — "evidence": "Keeper await-Bug seit Monaten offen. 5 BUILD_SPECS, 0 implementiert",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/data/fear_map.json:35 — "Keeper: await-Bug ein Einzeiler, seit Monaten offen",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/data/fear_map.json:39 — "micro_offer": "Ein Keeper-Bug fixen? 15 Min."
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/tests/test_bookmark_analyzer.py:1 — """Tests for BookmarkAnalyzer — parse, score, cache, fail-open."""
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/samuel/tests/test_bookmark_analyzer.py:134 — hugging_face = next(b for b in result if "huggingface" in b["url"])
+

Storyboard: samuel-474277b9a5.md · Video: samuel-474277b9a5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/samuel-cddebbb8a7.html b/ProjectIntakeTower/explainers/web/samuel-cddebbb8a7.html new file mode 100644 index 0000000000000000000000000000000000000000..5e50e3c1e8d9b7c4eef1c493af72343efc2d4ac5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/samuel-cddebbb8a7.html @@ -0,0 +1,6 @@ +samuel — Visual Explainer

ProjectIntakeTower Visual Explainer

samuel

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel

Tech: python · Score: 25 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/data/core_memory.md:38 — Denke auf Architektur-Niveau (Adapter Patterns, Fallback-Ketten, Trade-off-Matrizen). Aber Implementation bleibt lueckenhaft. 40+ Seiten ADD fuer ~700 Zeilen Code. Keeper await-Bug
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/data/fear_map.json:32 — "evidence": "Keeper await-Bug seit Monaten offen. 5 BUILD_SPECS, 0 implementiert",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/data/fear_map.json:35 — "Keeper: await-Bug ein Einzeiler, seit Monaten offen",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/data/fear_map.json:39 — "micro_offer": "Ein Keeper-Bug fixen? 15 Min."
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/tests/test_replay_parser.py:27 — "message": {"role": "user", "content": "Fix the bug"},
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/samuel/tests/test_pattern_detector.py:67 — hyperfocus = next(s for s in signals if s.pattern_type == "hyperfocus")
+

Storyboard: samuel-cddebbb8a7.md · Video: samuel-cddebbb8a7.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/samuel-os-v2-07f2a4768d.html b/ProjectIntakeTower/explainers/web/samuel-os-v2-07f2a4768d.html new file mode 100644 index 0000000000000000000000000000000000000000..1f97cb50cf8a0d4debc244aabd18658f29af3ae6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/samuel-os-v2-07f2a4768d.html @@ -0,0 +1,6 @@ +samuel-os-v2 — Visual Explainer

ProjectIntakeTower Visual Explainer

samuel-os-v2

/home/smlflg/Projekte/samuel-os-v2

Tech: docs/notes · Score: 38 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

samuel-os-v2 Persoenliches Arbeitssystem fuer fokussierte, lernfaehige AI-Engineering-Arbeit.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 12 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 12 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/samuel-os-v2/README.md:20 — - `WEEKLY.md`: Wochenziel, Review, Energie, Ablenkungen, Fokus.
  • /home/smlflg/Projekte/samuel-os-v2/README.md:51 — - Missionen geben Wochenfokus, ohne ein zweites Todo-System zu sein.
  • /home/smlflg/Projekte/samuel-os-v2/WEEKLY.md:29 — - [ ] Learning Loop: 1/3 Learnings extrahiert
  • /home/smlflg/Projekte/samuel-os-v2/WEEKLY.md:31 — - [ ] Inbox Shield: INBOX statt Scope-Flucht (2/7)
  • /home/smlflg/Projekte/samuel-os-v2/WEEKLY.md:46 — ## Review-Slots
  • /home/smlflg/Projekte/samuel-os-v2/WEEKLY.md:49 — - Weekly Review: 2026-03-30
+

Storyboard: samuel-os-v2-07f2a4768d.md · Video: samuel-os-v2-07f2a4768d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/samuel-system-1690f00467.html b/ProjectIntakeTower/explainers/web/samuel-system-1690f00467.html new file mode 100644 index 0000000000000000000000000000000000000000..5578f9826636bdf63103614b63539e58b0c0dd2e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/samuel-system-1690f00467.html @@ -0,0 +1,6 @@ +samuel-system — Visual Explainer

ProjectIntakeTower Visual Explainer

samuel-system

/home/smlflg/Projekte/LuckSurface/samuel-system

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Samuel.SYSTEM Samuel.SYSTEM is the public operating model for Samuel's agentic work.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: samuel-system-1690f00467.md · Video: samuel-system-1690f00467.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sandraswritingworld-9c951f9f13.html b/ProjectIntakeTower/explainers/web/sandraswritingworld-9c951f9f13.html new file mode 100644 index 0000000000000000000000000000000000000000..1c9ed1d486ab6549487af3bff975ecbc64dc9de7 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sandraswritingworld-9c951f9f13.html @@ -0,0 +1,6 @@ +SandrasWritingWorld — Visual Explainer

ProjectIntakeTower Visual Explainer

SandrasWritingWorld

/home/smlflg/Projekte/SandrasWritingWorld

Tech: docs/notes · Score: 40 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Your Website — SandrasWritingWorld Welcome!

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 31 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 31 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:101 — - Pixel-art board colors via cm-chessboard CSS overrides (black + crimson or black + gold — open question)
  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:163 — **No build step.** Pure static. Open `index.html` in a browser to develop locally.
  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:350 — ## 9. Open Questions for Sandra / Miran
  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:371 — - [ ] Navigate between all 6 pages: SoundCloud player never stops or restarts
  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:372 — - [ ] Home: U-Bahn video autoplays muted, loops, fills viewport
  • /home/smlflg/Projekte/SandrasWritingWorld/ARCHITECTURE.md:373 — - [ ] Home: "Welcome to the journey" overlay text visible over video
+

Storyboard: sandraswritingworld-9c951f9f13.md · Video: sandraswritingworld-9c951f9f13.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/schema-e571b59e0e.html b/ProjectIntakeTower/explainers/web/schema-e571b59e0e.html new file mode 100644 index 0000000000000000000000000000000000000000..960507d062fa972532b52f9dcf2d9164597712cd --- /dev/null +++ b/ProjectIntakeTower/explainers/web/schema-e571b59e0e.html @@ -0,0 +1,6 @@ +schema — Visual Explainer

ProjectIntakeTower Visual Explainer

schema

/home/smlflg/Projekte/Harness_swap/packages/schema

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: schema-e571b59e0e.md · Video: schema-e571b59e0e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/schloss_pdf-9fe7072a7c.html b/ProjectIntakeTower/explainers/web/schloss_pdf-9fe7072a7c.html new file mode 100644 index 0000000000000000000000000000000000000000..e8cc76079331b54b516613da9db162c927b77095 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/schloss_pdf-9fe7072a7c.html @@ -0,0 +1,6 @@ +schloss_PDF — Visual Explainer

ProjectIntakeTower Visual Explainer

schloss_PDF

/home/smlflg/Projekte/schloss_PDF

Tech: unknown · Score: 5 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 2 TODO/FIXME/WIP hints
  • plans/backlogs found
  • unclear purpose

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/schloss_PDF/OpenCode PDF Zusammenfassung_files/writing-block-editor-o0v3uy9j.css:1 — ._4ccM4G_magic-edit-selection{background:var(--theme-user-selection-bg,var(--selection));-webkit-box-decoration-break:clone;box-decoration-break:clone;padding:4.5px 0}[data-me-role
  • /home/smlflg/Projekte/schloss_PDF/.hermes/plans/2026-04-07_213045-bednke-was-dass-emotianl-f-r-mich-bedeutet.md:91 — **Opus 4.6:** Principle-first, Review-first, Senior-Analyst-Frame
+

Storyboard: schloss_pdf-9fe7072a7c.md · Video: schloss_pdf-9fe7072a7c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scim-8ee0630682.html b/ProjectIntakeTower/explainers/web/scim-8ee0630682.html new file mode 100644 index 0000000000000000000000000000000000000000..c1533d2a2621b0934b20a97e825c7328ce9bdba3 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scim-8ee0630682.html @@ -0,0 +1,6 @@ +scim — Visual Explainer

ProjectIntakeTower Visual Explainer

scim

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/management_endpoints/scim

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

SCIM v2 Integration for LiteLLM Proxy This module provides SCIM v2 (System for Cross-domain Identity Management) endpoints for LiteLLM Proxy, allowing identity providers to manage users and teams (groups) within the Lite

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/management_endpoints/scim/README_SCIM.md:7 — SCIM is an open standard designed to simplify user management across different systems. This implementation allows compatible identity providers (like Okta, Azure AD, OneLogin, etc
+

Storyboard: scim-8ee0630682.md · Video: scim-8ee0630682.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/screenshots-4876cc00af.html b/ProjectIntakeTower/explainers/web/screenshots-4876cc00af.html new file mode 100644 index 0000000000000000000000000000000000000000..7a14469e7c33410d9f240a701b23d1fb615687e8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/screenshots-4876cc00af.html @@ -0,0 +1,6 @@ +screenshots — Visual Explainer

ProjectIntakeTower Visual Explainer

screenshots

/home/smlflg/Projekte/learn-harness-engineering/docs/public/screenshots

Tech: docs/notes · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: screenshots-4876cc00af.md · Video: screenshots-4876cc00af.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-12ad857658.html b/ProjectIntakeTower/explainers/web/scripts-12ad857658.html new file mode 100644 index 0000000000000000000000000000000000000000..3af887727f7211b4a6e5a3747971b650f9404cec --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-12ad857658.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/dlm/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-12ad857658.md · Video: scripts-12ad857658.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-18a710a12f.html b/ProjectIntakeTower/explainers/web/scripts-18a710a12f.html new file mode 100644 index 0000000000000000000000000000000000000000..9981f9905357019f4a77cc530cdde7e614687b8d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-18a710a12f.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/smk/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-18a710a12f.md · Video: scripts-18a710a12f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-57575003f0.html b/ProjectIntakeTower/explainers/web/scripts-57575003f0.html new file mode 100644 index 0000000000000000000000000000000000000000..75315e51fd929cde3736e4abaa6012f1c92ed825 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-57575003f0.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/fixer/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-57575003f0.md · Video: scripts-57575003f0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-5e89206969.html b/ProjectIntakeTower/explainers/web/scripts-5e89206969.html new file mode 100644 index 0000000000000000000000000000000000000000..e6c7f091b1747f78b28d1e7182c3afe0d0a919fe --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-5e89206969.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/voice-learning/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-5e89206969.md · Video: scripts-5e89206969.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-617f385573.html b/ProjectIntakeTower/explainers/web/scripts-617f385573.html new file mode 100644 index 0000000000000000000000000000000000000000..089c6e4f03b94f8554ec897ef37a50d4bb33ae85 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-617f385573.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/decision-control/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-617f385573.md · Video: scripts-617f385573.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-b70185e298.html b/ProjectIntakeTower/explainers/web/scripts-b70185e298.html new file mode 100644 index 0000000000000000000000000000000000000000..9512386a2d94acbcf7255d9e23a999eb93d1d218 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-b70185e298.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/ra/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-b70185e298.md · Video: scripts-b70185e298.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-e206d00442.html b/ProjectIntakeTower/explainers/web/scripts-e206d00442.html new file mode 100644 index 0000000000000000000000000000000000000000..f005c836a3eda0c85456c2fe3c7a596e4067951e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-e206d00442.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/diagnosis/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-e206d00442.md · Video: scripts-e206d00442.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-f22bd304ed.html b/ProjectIntakeTower/explainers/web/scripts-f22bd304ed.html new file mode 100644 index 0000000000000000000000000000000000000000..697122db979a59634bcf05e1920c8a217d63047f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-f22bd304ed.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-f22bd304ed.md · Video: scripts-f22bd304ed.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/scripts-f979721f5a.html b/ProjectIntakeTower/explainers/web/scripts-f979721f5a.html new file mode 100644 index 0000000000000000000000000000000000000000..54e9ef9769f20204c8d25ffb442fed1eadf1dc3b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/scripts-f979721f5a.html @@ -0,0 +1,6 @@ +scripts — Visual Explainer

ProjectIntakeTower Visual Explainer

scripts

/home/smlflg/.hermes/profiles/mlg/skills/productivity/google-workspace/scripts

Tech: python · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: scripts-f979721f5a.md · Video: scripts-f979721f5a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sdists-v9-be92bdb037.html b/ProjectIntakeTower/explainers/web/sdists-v9-be92bdb037.html new file mode 100644 index 0000000000000000000000000000000000000000..86501c212bdf42d9cb806da6e04a62a911fe9b68 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sdists-v9-be92bdb037.html @@ -0,0 +1,6 @@ +sdists-v9 — Visual Explainer

ProjectIntakeTower Visual Explainer

sdists-v9

/home/smlflg/.hermes/.uv-cache/sdists-v9

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: sdists-v9-be92bdb037.md · Video: sdists-v9-be92bdb037.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sdists-v9-c396947c6e.html b/ProjectIntakeTower/explainers/web/sdists-v9-c396947c6e.html new file mode 100644 index 0000000000000000000000000000000000000000..8961c2882c6ca610f4c3bf29ec0f7334cd10639c --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sdists-v9-c396947c6e.html @@ -0,0 +1,6 @@ +sdists-v9 — Visual Explainer

ProjectIntakeTower Visual Explainer

sdists-v9

/home/smlflg/Projekte/Connector/google-workspace/state/cache/uv/sdists-v9

Tech: unknown · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt unknown, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • unclear purpose

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: sdists-v9-c396947c6e.md · Video: sdists-v9-c396947c6e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/searchagent-7ebc193f7e.html b/ProjectIntakeTower/explainers/web/searchagent-7ebc193f7e.html new file mode 100644 index 0000000000000000000000000000000000000000..35aeb8bb1b2ab35952caa6ed06f386f934cb33e8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/searchagent-7ebc193f7e.html @@ -0,0 +1,6 @@ +SearchAgent — Visual Explainer

ProjectIntakeTower Visual Explainer

SearchAgent

/home/smlflg/Projekte/SearchAgent

Tech: python · Score: 16 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

SearchAgent Archived learning project.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/SearchAgent/FOR_SMLFLG.md:53 — ## Next Steps (wenn weiterbauen)
+

Storyboard: searchagent-7ebc193f7e.md · Video: searchagent-7ebc193f7e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/self_investment-9cc895ec7e.html b/ProjectIntakeTower/explainers/web/self_investment-9cc895ec7e.html new file mode 100644 index 0000000000000000000000000000000000000000..eb61e70b96856680160e59bcc003d82eade188e3 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/self_investment-9cc895ec7e.html @@ -0,0 +1,6 @@ +self_investment — Visual Explainer

ProjectIntakeTower Visual Explainer

self_investment

/home/smlflg/Projekte/Amazon/self_investment

Tech: docs/notes · Score: 32 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Self-Investment Operating Plan Start date: 2026-05-04 This folder turns the 15k net self-investment plan into an executable routine.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 13 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 13 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Amazon/self_investment/tracker.py:23 — with path.open(newline="", encoding="utf-8") as handle:
  • /home/smlflg/Projekte/Amazon/self_investment/tracker.py:28 — with path.open("w", newline="", encoding="utf-8") as handle:
  • /home/smlflg/Projekte/Amazon/self_investment/tracker.py:98 — print(f"Next {args.limit} tasks")
  • /home/smlflg/Projekte/Amazon/self_investment/tracker.py:135 — next_tasks = sub.add_parser("next", help="Show next open tasks")
  • /home/smlflg/Projekte/Amazon/self_investment/weekly_review.md:1 — # Weekly Review
  • /home/smlflg/Projekte/Amazon/self_investment/weekly_review.md:33 — Next week's 3 tasks:
+

Storyboard: self_investment-9cc895ec7e.md · Video: self_investment-9cc895ec7e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/server-8bd5de99fa.html b/ProjectIntakeTower/explainers/web/server-8bd5de99fa.html new file mode 100644 index 0000000000000000000000000000000000000000..99aba53548b77675a9a3c94594151297d426abea --- /dev/null +++ b/ProjectIntakeTower/explainers/web/server-8bd5de99fa.html @@ -0,0 +1,6 @@ +server — Visual Explainer

ProjectIntakeTower Visual Explainer

server

/home/smlflg/Projekte/PseudoLogikPyhthonCPP/server

Tech: node, typescript · Score: 24 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, typescript, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 12 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 12 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/logicParser.ts:95 — const next = nonEmpty[i + 1];
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/logicParser.ts:96 — const nextIndent = next?.raw.match(/^ */)?.[0].length ?? -1;
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/logicParser.ts:97 — if (!next || nextIndent <= indent) {
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/fsrs.ts:50 — review: log.review.toISOString(),
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/fsrs.ts:75 — const result = scheduler.next(previous, new Date(), ratingFromGrade(grade));
  • /home/smlflg/Projekte/PseudoLogikPyhthonCPP/server/src/fsrs.ts:79 — next: serializeCard(result.card),
+

Storyboard: server-8bd5de99fa.md · Video: server-8bd5de99fa.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/session-browser-257de3e006.html b/ProjectIntakeTower/explainers/web/session-browser-257de3e006.html new file mode 100644 index 0000000000000000000000000000000000000000..43209f0a522d9a31f664f5547d57df1ebe53c42e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/session-browser-257de3e006.html @@ -0,0 +1,6 @@ +session-browser — Visual Explainer

ProjectIntakeTower Visual Explainer

session-browser

/home/smlflg/Projekte/MyAIGame/session-browser

Tech: python · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 5 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 5 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/MyAIGame/session-browser/session_parser.py:153 — with open(filepath, "r", encoding="utf-8", errors="replace") as f:
  • /home/smlflg/Projekte/MyAIGame/session-browser/session_parser.py:163 — with open(filepath, "r", encoding="utf-8", errors="replace") as f:
  • /home/smlflg/Projekte/MyAIGame/session-browser/session_parser.py:272 — with open(path, "r", encoding="utf-8", errors="replace") as f:
  • /home/smlflg/Projekte/MyAIGame/session-browser/session_parser.py:442 — with open(path, "r", encoding="utf-8", errors="replace") as f:
  • /home/smlflg/Projekte/MyAIGame/session-browser/session_parser.py:458 — # Gather context lines (previous + next)
+

Storyboard: session-browser-257de3e006.md · Video: session-browser-257de3e006.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/shared-66bb41fa0c.html b/ProjectIntakeTower/explainers/web/shared-66bb41fa0c.html new file mode 100644 index 0000000000000000000000000000000000000000..6d65295d2452264364fafa6e41fd9b654cbfcbb5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/shared-66bb41fa0c.html @@ -0,0 +1,6 @@ +shared — Visual Explainer

ProjectIntakeTower Visual Explainer

shared

/home/smlflg/Projekte/learn-harness-engineering/projects/shared

Tech: node, typescript · Score: 5 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/shared/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/shared/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
+

Storyboard: shared-66bb41fa0c.md · Video: shared-66bb41fa0c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/shared-gui-39cb40d2b3.html b/ProjectIntakeTower/explainers/web/shared-gui-39cb40d2b3.html new file mode 100644 index 0000000000000000000000000000000000000000..495d202b4a5b8b61eff7dda2db0e7d57404ae119 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/shared-gui-39cb40d2b3.html @@ -0,0 +1,6 @@ +shared-gui — Visual Explainer

ProjectIntakeTower Visual Explainer

shared-gui

/home/smlflg/Projekte/shared-gui

Tech: python · Score: 19 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

shared-gui — GTK3 Base Class Shared GTK3 base for all desktop apps in this setup.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 2 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/shared-gui/FOR_SMLFLG.md:70 — - Kein Packaging/`__init__.py` — direkter Import via sys.path Hack
  • /home/smlflg/Projekte/shared-gui/FOR_SMLFLG.md:81 — ## Next Steps
+

Storyboard: shared-gui-39cb40d2b3.md · Video: shared-gui-39cb40d2b3.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/shortcutcounter-d2ffa4d801.html b/ProjectIntakeTower/explainers/web/shortcutcounter-d2ffa4d801.html new file mode 100644 index 0000000000000000000000000000000000000000..c8b1c4127996c02642bbfda6318995b531870a44 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/shortcutcounter-d2ffa4d801.html @@ -0,0 +1,6 @@ +ShortcutCounter — Visual Explainer

ProjectIntakeTower Visual Explainer

ShortcutCounter

/home/smlflg/Projekte/ShortcutCounter

Tech: python · Score: 51 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ShortcutCounter Passive keyboard shortcut tracker for Linux/Wayland.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise, uncommitted changes, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 8 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:5 — Monster-Session: 5-Agent Team Sprint (openclaw-sprint) mit Research, Architektur, Builder, Tester, Coach. Danach /simplify Review mit 3 Fixes. Session-Feedback: Sidecar Suggestions
  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:10 — - [ ] ShortcutCounter committen: `storage.py` (dead tomli fallback entfernt), `services/shortcut-counter.service` (StartLimit → [Unit]), `pyproject.toml` (toml dep entfernt)
  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:11 — - [ ] OpenClaw docs committen: 10 neue READMEs in `~/opencode/openclaw/docs-samuel/` + 3 Fixes (Kommentar, Cron-Snippet, PRIOR_ART.md)
  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:14 — - [ ] Telefonnummer in `~/opencode/openclaw/HOWTO-SAMUEL.md` Zeile 257 — rauslöschen oder lassen?
  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:17 — - [ ] Sidecar Suggestion-Logik phase-aware machen:
  • /home/smlflg/Projekte/ShortcutCounter/PLAN_2026-03-05_sprint-cleanup.md:24 — - [ ] /learn — Agent Teams Workflow verinnerlichen (was hat Samuel verstanden?)
+

Storyboard: shortcutcounter-d2ffa4d801.md · Video: shortcutcounter-d2ffa4d801.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidebyside-050b659506.html b/ProjectIntakeTower/explainers/web/sidebyside-050b659506.html new file mode 100644 index 0000000000000000000000000000000000000000..2566624654318d661d12343ce3aa55006578ae53 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidebyside-050b659506.html @@ -0,0 +1,6 @@ +sidebyside — Visual Explainer

ProjectIntakeTower Visual Explainer

sidebyside

/home/smlflg/Projekte/HarnessEcosystem/sidebyside

Tech: docs/notes · Score: 22 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidebyside Harness Snapshot Standalone statische SPA fuer `data/harness-snapshot.json`.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 8 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/app.js:567 — ui.dialog.showModal ? ui.dialog.showModal() : ui.dialog.setAttribute("open", "");
  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/app.js:572 — if (ui.dialog.open) ui.dialog.close();
  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/scripts/extract_hermes.py:391 — warnings.append(f"unable to open state db {path}: {exc}")
  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/scripts/extract_claude.py:214 — with path.open("r", encoding="utf-8", errors="replace") as handle:
  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/scripts/extract_claude.py:255 — with file_path.open("r", encoding="utf-8", errors="replace") as handle:
  • /home/smlflg/Projekte/HarnessEcosystem/sidebyside/scripts/extract_codex.py:201 — with path.open("rb") as fh:
+

Storyboard: sidebyside-050b659506.md · Video: sidebyside-050b659506.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-93e2e4592e.html b/ProjectIntakeTower/explainers/web/sidecar-93e2e4592e.html new file mode 100644 index 0000000000000000000000000000000000000000..d290592b1f623c4afa1fcb975cb6c913467821e1 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-93e2e4592e.html @@ -0,0 +1,6 @@ +Sidecar — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar

Tech: docs/notes · Score: 63 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar v5 — Quality Control for Claude Code A persistent daemon that monitors Claude Code in real-time and injects situational context.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes, 4 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, hoher Intake-Score, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/content_detectors.py:34 — with open("/tmp/claude-sidecar.log", "a") as f:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/florian_tts.py:35 — with open(LOG_PATH, "a") as f:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/florian_tts.py:179 — with open(AUDIO_LOCK_PATH, "a+", encoding="utf-8") as lock_file:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/context_selector.py:134 — with open("/tmp/claude-sidecar.log", "a") as f:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/sidecar.py:140 — with open(LOG_PATH, "a") as f:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar/sidecar.py:196 — "keywords": ["fix", "nur hier", "subsystem", "bug"],
+

Storyboard: sidecar-93e2e4592e.md · Video: sidecar-93e2e4592e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-ng-6382aa0e95.html b/ProjectIntakeTower/explainers/web/sidecar-ng-6382aa0e95.html new file mode 100644 index 0000000000000000000000000000000000000000..bf67cf64d2cad549792c132cde588f16649ed073 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-ng-6382aa0e95.html @@ -0,0 +1,6 @@ +Sidecar-ng — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-ng

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng

Tech: docs/notes · Score: 59 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar-NG Stateless Context Injection Hook for Claude Code.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_results.json:225 — "category": "SKILL: review",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_results.json:226 — "expected": "SKILL: review",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_results.json:227 — "got_rule": "WICHTIG: Lies zuerst ~/Projekte/Sidecar-ng/knowledge/commands/review.md und befolge den Workflow.",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_results.json:230 — "prompt_short": "mach ein code review von den heutigen änderungen"
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_ab_results.json:227 — "category": "SKILL: review",
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng/eval_ab_results.json:228 — "expected": "SKILL: review",
+

Storyboard: sidecar-ng-6382aa0e95.md · Video: sidecar-ng-6382aa0e95.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-ng-dashboard-8736c7518e.html b/ProjectIntakeTower/explainers/web/sidecar-ng-dashboard-8736c7518e.html new file mode 100644 index 0000000000000000000000000000000000000000..baa98876f8e87860bd3e6665e1125df7b1047127 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-ng-dashboard-8736c7518e.html @@ -0,0 +1,6 @@ +Sidecar-ng-dashboard — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-ng-dashboard

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard

Tech: agent, python · Score: 50 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar-NG Dashboard A standalone web dashboard for monitoring and managing Sidecar-NG, a prompt-classifier with keyword-first pre-filtering and LLM-fallback chaining.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 15 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 15 TODO/FIXME/WIP hints
  • README present
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:91 — "defaults": ["Repository scope", "Bug and regression review"],
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:121 — "defaults": ["Current topic", "Open research question"],
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:250 — current = next(provider for provider in providers if provider["name"] == provider_name)
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:280 — updated = next(
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:336 — dashboard_session = next(
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard/control_service.py:385 — updated = next(mode for mode in list_modes() if mode["name"] == mode_name)
+

Storyboard: sidecar-ng-dashboard-8736c7518e.md · Video: sidecar-ng-dashboard-8736c7518e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v5-ee6c377f82.html b/ProjectIntakeTower/explainers/web/sidecar-v5-ee6c377f82.html new file mode 100644 index 0000000000000000000000000000000000000000..a892eac4fe15f7a78bedef2a4f3072b15014b792 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v5-ee6c377f82.html @@ -0,0 +1,6 @@ +Sidecar-V5 — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V5

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5

Tech: python · Score: 58 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar V5 — Personal Context Awareness Standalone asyncio daemon that injects personal context about Samuel into Claude Code.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 12 TODO/FIXME-Hinweise, uncommitted changes

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 12 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/sidecar_v5.py:137 — Fail-open: bei jedem Fehler {} zurueckgeben.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/sidecar_v5.py:166 — # IRON RULE: Never crash. Fail-open.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/v5_bridge.py:8 — Fail-open: bei jedem Fehler leeren Output, Claude arbeitet weiter.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/v5_bridge.py:74 — # Daemon nicht erreichbar oder Fehler → fail-open
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/FOR_SMLFLG.md:70 — - Asyncio Unix Socket Server mit Fail-Open (jeder Fehler → leere Antwort, kein Crash)
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5/FOR_SMLFLG.md:89 — - **Fail-Open als Iron Rule**: Jeder try/except gibt `{}` zurueck. Profil-Laden fehlgeschlagen = degraded mode, kein Absturz.
+

Storyboard: sidecar-v5-ee6c377f82.md · Video: sidecar-v5-ee6c377f82.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v6-bf4e8dc3cb.html b/ProjectIntakeTower/explainers/web/sidecar-v6-bf4e8dc3cb.html new file mode 100644 index 0000000000000000000000000000000000000000..d4360a6f56ecbe70523a993a6e0696ce8b67a642 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v6-bf4e8dc3cb.html @@ -0,0 +1,6 @@ +Sidecar-V6 — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V6

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6

Tech: agent, python · Score: 56 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar V6 AI Coaching Companion fuer Claude Code — beobachtet deine Coding-Sessions und gibt ADHS-aware Nudges, trackt Mechanismen mit Voting, und hat einen MiniMax Slow-Path fuer tiefere Analyse.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 7 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/PLAN_2026-03-09_AGENTISCHE-MECHANISMEN.md:150 — ## Fail-Open
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/architektur-v6.html:1342 — <div class="mech-desc">Blockiert neue Projekte wenn aktive unfertig sind. WIP-Limit.</div>
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/architektur-v6.html:1359 — <div class="mech-name">Weekly Review</div>
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/architektur-v6.html:1458 — <div class="mech-name">Review-Vorschlag</div>
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/TODO_dashboard.md:1 — # TODO: Dashboard + Panel End-to-End verdrahten
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6/TODO_dashboard.md:75 — - [ ] `/api/xp` returned XP-Bar Partial mit Level, XP today, Streak
+

Storyboard: sidecar-v6-bf4e8dc3cb.md · Video: sidecar-v6-bf4e8dc3cb.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v7-ed034c870d.html b/ProjectIntakeTower/explainers/web/sidecar-v7-ed034c870d.html new file mode 100644 index 0000000000000000000000000000000000000000..2727e10ab6ad92188a2a0503312e8b7222c1a81a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v7-ed034c870d.html @@ -0,0 +1,6 @@ +Sidecar-V7 — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V7

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7

Tech: agent, python · Score: 77 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar V7 **Context-aware ADHS coaching daemon for AI coding assistants.** Why Developers with ADHD face specific challenges when coding with AI assistants: hyperfocus without breaks, session sprawl across too many proj

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes, 8 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, hoher Intake-Score, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/FOR_SMLFLG.md:36 — Jede Quelle ist fail-open: wenn eine Quelle ausfaellt, funktioniert der Rest weiter.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/FOR_SMLFLG.md:50 — | V6 core/ | daemon.py, coach.py, ... | core/sidecar_core/ | v6→v7 Rename, Bug-Fixes |
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/FOR_SMLFLG.md:116 — - Fail-Open ist Pflicht: Daemon darf Claude Code nie blockieren
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/FOR_SMLFLG.md:125 — - `_check_should_speak()` — Neue Methode die `tts_ranker.should_speak()` aus `samuel/sidecar_samuel/tts_ranker.py` verdrahtet. Fail-open Gate: wenn eine Mechanismus+msg_type+phase+
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/FOR_SMLFLG.md:149 — **Fail-open Gate:** Wenn keine Daten da sind oder DB-Error → erlauben. Nur blockieren wenn genug negative Bewertungen vorliegen. Sicherer Default weil ein stummes System nervoser m
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7/README.md:11 — Developers with ADHD face specific challenges when coding with AI assistants: hyperfocus without breaks, session sprawl across too many projects, and no awareness of energy pattern
+

Storyboard: sidecar-v7-ed034c870d.md · Video: sidecar-v7-ed034c870d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v7-lite-323322aa5b.html b/ProjectIntakeTower/explainers/web/sidecar-v7-lite-323322aa5b.html new file mode 100644 index 0000000000000000000000000000000000000000..7d918c67d9edeb683d48cc5985d38a524bea780e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v7-lite-323322aa5b.html @@ -0,0 +1,6 @@ +Sidecar-V7-Lite — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V7-Lite

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite

Tech: python · Score: 37 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, uncommitted changes, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 4 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite/PLAN_V7_LITE_M2.7.md:266 — - and the agent type is long-running or open-ended
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite/sidecar_lite/bridge.py:68 — # Fail-open: any error means we don't block Claude
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite/sidecar_lite/session.py:119 — with open(path, "w") as f:
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite/sidecar_lite/session.py:128 — with open(path) as f:
+

Storyboard: sidecar-v7-lite-323322aa5b.md · Video: sidecar-v7-lite-323322aa5b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v7-v2-520073a262.html b/ProjectIntakeTower/explainers/web/sidecar-v7-v2-520073a262.html new file mode 100644 index 0000000000000000000000000000000000000000..e8b8afc74611a35c681218feb439467f4335cf64 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v7-v2-520073a262.html @@ -0,0 +1,6 @@ +Sidecar-V7-V2 — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V7-V2

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2

Tech: python · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 3 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/FORENSIK.md:51 — 22:04–22:38 Autonomous Loop Bug-Fix
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/FORENSIK.md:271 — **Warum:** `c27535f` "Mega-Session: Alignment Fix + Quality P0/P1" — ein Commit für eine gesamte Session macht Review unmöglich und versteckt Scope-Creep.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/FORENSIK.md:275 — ### R6: Observer-Peer-Review bei selbstreferenziellem Bau
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/FORENSIK.md:277 — **Was:** Wenn Claude Sidecar selbst baut, wird nach jedem Feature ein externes Review gemacht (Codex oder MiniMax) mit der Frage: "Löst das das ursprüngliche Problem besser oder ba
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/HANDOFF.md:567 — 5. **Safety als "optional aber blockt"** — fail-open bei Load-Fehler. Unveraendert uebernehmen, kein Umbau.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-V2/HANDOFF.md:627 — """Dispatch ein Event zum registrierten Handler. Fail-open."""
+

Storyboard: sidecar-v7-v2-520073a262.md · Video: sidecar-v7-v2-520073a262.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v8-9f03a02b07.html b/ProjectIntakeTower/explainers/web/sidecar-v8-9f03a02b07.html new file mode 100644 index 0000000000000000000000000000000000000000..c69d181f9aa49cb47e8cb6e3435e28efd17f561e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v8-9f03a02b07.html @@ -0,0 +1,6 @@ +Sidecar-V8 — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V8

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8

Tech: agent, python · Score: 60 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar V8 Implementation repository for `Sidecar V8`.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise, uncommitted changes

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, hoher Intake-Score, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 8 TODO/FIXME/WIP hints
  • README present
  • agentized

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/AGENTS.md:17 — - `Codex`: implementation, test execution, review, technical validation
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/AGENTS.md:42 — - Keep canonical decisions in sync with the plan repo if implementation reveals a plan bug.
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/core/tests/test_phase_tracker.py:17 — assert tracker.update_from_prompt("fix this bug") == "debugging"
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/core/tests/test_phase_tracker.py:79 — tracker.record_event({"type": "prompt", "content": "fix the login bug now"})
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/core/tests/test_phase_tracker.py:80 — tracker.record_event({"type": "prompt", "content": "fix the login bug please"})
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8/core/tests/test_context.py:104 — state.last_safety_warning = "[SIDECAR-V8] Warning: possible secret exposure detected. Please review."
+

Storyboard: sidecar-v8-9f03a02b07.md · Video: sidecar-v8-9f03a02b07.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecar-v8-plan-d6f06ac5d8.html b/ProjectIntakeTower/explainers/web/sidecar-v8-plan-d6f06ac5d8.html new file mode 100644 index 0000000000000000000000000000000000000000..3949cfe1198c6cf44cb6b8c440b445097440a487 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecar-v8-plan-d6f06ac5d8.html @@ -0,0 +1,6 @@ +Sidecar-V8-Plan — Visual Explainer

ProjectIntakeTower Visual Explainer

Sidecar-V8-Plan

/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan

Tech: docs/notes · Score: 59 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Sidecar V8 Plan Canonical planning repository for `Sidecar V8`.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/README.md:72 — | E8 | Knowledge Objects — consolidate or drop? | open |
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/.github/pull_request_template.md:29 — ## Human Review Needed?
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/.github/ISSUE_TEMPLATE/agent_job_contract.md:19 — - [ ] `READ_ONLY_AUDIT`
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/.github/ISSUE_TEMPLATE/agent_job_contract.md:20 — - [ ] `TEST_GENERATION`
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/.github/ISSUE_TEMPLATE/agent_job_contract.md:21 — - [ ] `SMALL_FIX`
  • /home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/.github/ISSUE_TEMPLATE/agent_job_contract.md:22 — - [ ] `REFACTOR_PLAN_ONLY`
+

Storyboard: sidecar-v8-plan-d6f06ac5d8.md · Video: sidecar-v8-plan-d6f06ac5d8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sidecardashboard-10c973f6a7.html b/ProjectIntakeTower/explainers/web/sidecardashboard-10c973f6a7.html new file mode 100644 index 0000000000000000000000000000000000000000..bc7d575ec8cfa14e59ffd8254c75bb2a1f74b474 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sidecardashboard-10c973f6a7.html @@ -0,0 +1,6 @@ +SidecarDashboard — Visual Explainer

ProjectIntakeTower Visual Explainer

SidecarDashboard

/home/smlflg/Projekte/Sidecar-Workspace/SidecarDashboard

Tech: agent, python · Score: 18 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Sidecar/Coaching-Layer, der AI-Coding-Sessions beobachtet und sicherer, fokussierter und weniger chaotisch macht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: sidecardashboard-10c973f6a7.md · Video: sidecardashboard-10c973f6a7.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/single-role-325160d775.html b/ProjectIntakeTower/explainers/web/single-role-325160d775.html new file mode 100644 index 0000000000000000000000000000000000000000..691d54680499b14c9bb1d6bd760b5dab130c1d9c --- /dev/null +++ b/ProjectIntakeTower/explainers/web/single-role-325160d775.html @@ -0,0 +1,6 @@ +single-role — Visual Explainer

ProjectIntakeTower Visual Explainer

single-role

/home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role

Tech: agent, node, typescript · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 25 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 25 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/solution/single-role/clean-state-checklist.md:15 — - [ ] No React imports in services or main process
+

Storyboard: single-role-325160d775.md · Video: single-role-325160d775.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/skills-3a3285b8ea.html b/ProjectIntakeTower/explainers/web/skills-3a3285b8ea.html new file mode 100644 index 0000000000000000000000000000000000000000..740f0814215657d6cc107d1b6ec1a05f913fc0ef --- /dev/null +++ b/ProjectIntakeTower/explainers/web/skills-3a3285b8ea.html @@ -0,0 +1,6 @@ +skills — Visual Explainer

ProjectIntakeTower Visual Explainer

skills

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/litellm_proxy/skills

Tech: docs/notes · Score: 12 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LiteLLM Skills - Database-Backed Skills Storage This module provides database-backed skills storage as an alternative to Anthropic's cloud-based Skills API.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 3 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/litellm_proxy/skills/README.md:246 — files=[open("data-analysis.zip", "rb")],
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/litellm_proxy/skills/sandbox_executor.py:101 — with open(local_path, "wb") as f:
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/litellm_proxy/skills/sandbox_executor.py:243 — with open(tmp_path, "rb") as f:
+

Storyboard: skills-3a3285b8ea.md · Video: skills-3a3285b8ea.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/skills-7c8a2825fa.html b/ProjectIntakeTower/explainers/web/skills-7c8a2825fa.html new file mode 100644 index 0000000000000000000000000000000000000000..6bd8048ca9be05d762d4ca79af0cc56e2e17df93 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/skills-7c8a2825fa.html @@ -0,0 +1,6 @@ +skills — Visual Explainer

ProjectIntakeTower Visual Explainer

skills

/home/smlflg/Projekte/learn-harness-engineering/skills

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Skills [中文版](./README-CN.md) This directory contains reusable AI agent skills for the Learn Harness Engineering project.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:196 — - [ ] Implementation complete
  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:197 — - [ ] Verification passed
  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:198 — - [ ] Evidence recorded
  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:199 — - [ ] Repository restartable
  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:335 — 3. **Extraction timing creates race window** — User can start next turn before background extraction completes.
  • /home/smlflg/Projekte/learn-harness-engineering/skills/harness-creator/SKILL.md:350 — 违反这些非明显原则会导致 bug:
+

Storyboard: skills-7c8a2825fa.md · Video: skills-7c8a2825fa.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/skills-e21ab65783.html b/ProjectIntakeTower/explainers/web/skills-e21ab65783.html new file mode 100644 index 0000000000000000000000000000000000000000..e61354e9a5fbf7799341e4f1a4027eae623bf6de --- /dev/null +++ b/ProjectIntakeTower/explainers/web/skills-e21ab65783.html @@ -0,0 +1,6 @@ +skills — Visual Explainer

ProjectIntakeTower Visual Explainer

skills

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/anthropic/skills

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Anthropic Skills API Integration This module provides comprehensive support for the Anthropic Skills API through LiteLLM.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/anthropic/skills/readme.md:69 — # Get next page if available
  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/llms/anthropic/skills/readme.md:188 — - `next_page` (str, optional): Pagination token for the next page
+

Storyboard: skills-e21ab65783.md · Video: skills-e21ab65783.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/slackalerting-f9ff5ba89b.html b/ProjectIntakeTower/explainers/web/slackalerting-f9ff5ba89b.html new file mode 100644 index 0000000000000000000000000000000000000000..3253b468e8dffe02e09db9ca721135f311a2d58a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/slackalerting-f9ff5ba89b.html @@ -0,0 +1,6 @@ +SlackAlerting — Visual Explainer

ProjectIntakeTower Visual Explainer

SlackAlerting

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/integrations/SlackAlerting

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Slack Alerting on LiteLLM Gateway This folder contains the Slack Alerting integration for LiteLLM Gateway.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/integrations/SlackAlerting/slack_alerting.py:1347 — API requests will be rejected until either (a) you increase your monthly budget or (b) your monthly usage resets at the beginning of the next calendar month. <br /> <br />
+

Storyboard: slackalerting-f9ff5ba89b.md · Video: slackalerting-f9ff5ba89b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/smlfg-bd1773137b.html b/ProjectIntakeTower/explainers/web/smlfg-bd1773137b.html new file mode 100644 index 0000000000000000000000000000000000000000..8e3c331f05204c6c28567d74b68f502efc00cf63 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/smlfg-bd1773137b.html @@ -0,0 +1,6 @@ +smlfg — Visual Explainer

ProjectIntakeTower Visual Explainer

smlfg

/home/smlflg/Projekte/LuckSurface/smlfg

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Samuel Fleig Agentic operator / meta-engineer for AI-coding workflows.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/LuckSurface/smlfg/README.md:9 — - **Build agentic workflows:** context packs, routing, review loops, human-in-the-loop boundaries.
  • /home/smlflg/Projekte/LuckSurface/smlfg/README.md:11 — - **Evaluate behavior:** turn fuzzy prompt/workflow impressions into runs, comparisons, failures, and next steps.
+

Storyboard: smlfg-bd1773137b.md · Video: smlfg-bd1773137b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solid-ec3d38ffe8.html b/ProjectIntakeTower/explainers/web/solid-ec3d38ffe8.html new file mode 100644 index 0000000000000000000000000000000000000000..5b4a3e90483828ecf3e7e74686ca0f7451bef12f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solid-ec3d38ffe8.html @@ -0,0 +1,6 @@ +solid — Visual Explainer

ProjectIntakeTower Visual Explainer

solid

/home/smlflg/Projekte/symphony/elixir/deps/solid

Tech: docs/notes · Score: 18 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Solid Solid is an implementation in Elixir of the [Liquid](https://shopify.github.io/liquid/) template language with strict parsing.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 6 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 6 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:3 — ## Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:12 — ## Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:28 — ## Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:34 — * Fix `replace_last` filter bug with duplicate substrings
  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:40 — ## Bug fixes
  • /home/smlflg/Projekte/symphony/elixir/deps/solid/CHANGELOG.md:53 — ## Bug fixes
+

Storyboard: solid-ec3d38ffe8.md · Video: solid-ec3d38ffe8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solution-24369842ef.html b/ProjectIntakeTower/explainers/web/solution-24369842ef.html new file mode 100644 index 0000000000000000000000000000000000000000..8290efae50b7062893ec62489986e8b1a3f2a45a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solution-24369842ef.html @@ -0,0 +1,6 @@ +solution — Visual Explainer

ProjectIntakeTower Visual Explainer

solution

/home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution

Tech: agent, node, typescript · Score: 35 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • agentized

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/claude-progress.md:40 — **Next session**: No remaining features. Project 06 is complete.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:9 — - [ ] No TypeScript warnings about unused variables or imports
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code (`src/renderer/`)
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/solution/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code (`src/services/`)
+

Storyboard: solution-24369842ef.md · Video: solution-24369842ef.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solution-29b8e9044f.html b/ProjectIntakeTower/explainers/web/solution-29b8e9044f.html new file mode 100644 index 0000000000000000000000000000000000000000..7fc8fa347ef5131f762f3cc52b0f05dfe7a71022 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solution-29b8e9044f.html @@ -0,0 +1,6 @@ +solution — Visual Explainer

ProjectIntakeTower Visual Explainer

solution

/home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution

Tech: agent, node, typescript · Score: 17 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 3 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/claude-progress.md:27 — **Next session**: Proceed to Project 02 to add import, detail view, and persistence features.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/solution/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
+

Storyboard: solution-29b8e9044f.md · Video: solution-29b8e9044f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solution-5c505f1d56.html b/ProjectIntakeTower/explainers/web/solution-5c505f1d56.html new file mode 100644 index 0000000000000000000000000000000000000000..bda37d950fd0a557198a07cad7ef4d58f0e265bb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solution-5c505f1d56.html @@ -0,0 +1,6 @@ +solution — Visual Explainer

ProjectIntakeTower Visual Explainer

solution

/home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution

Tech: agent, node, typescript · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 24 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 24 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/solution/clean-state-checklist.md:15 — - [ ] No React imports in services or main process
+

Storyboard: solution-5c505f1d56.md · Video: solution-5c505f1d56.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solution-b44612ff4e.html b/ProjectIntakeTower/explainers/web/solution-b44612ff4e.html new file mode 100644 index 0000000000000000000000000000000000000000..0099ab23109d817b13e54444a0c1fc36995366cb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solution-b44612ff4e.html @@ -0,0 +1,6 @@ +solution — Visual Explainer

ProjectIntakeTower Visual Explainer

solution

/home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution

Tech: agent, node, typescript · Score: 20 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/session-handoff.md:41 — - The one-feature-at-a-time policy from AGENTS.md was followed strictly: each feature was implemented, verified, and recorded before moving to the next.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/session-handoff.md:66 — ### Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/AGENTS.md:24 — 6. **Only then** move to the next feature.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
+

Storyboard: solution-b44612ff4e.md · Video: solution-b44612ff4e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/solution-e1178ac8ec.html b/ProjectIntakeTower/explainers/web/solution-e1178ac8ec.html new file mode 100644 index 0000000000000000000000000000000000000000..0254361c55e6f2a067def3db47207c7c688a615a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/solution-e1178ac8ec.html @@ -0,0 +1,6 @@ +solution — Visual Explainer

ProjectIntakeTower Visual Explainer

solution

/home/smlflg/Projekte/learn-harness-engineering/projects/project-02/solution

Tech: agent, node, typescript · Score: 16 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/solution/session-handoff.md:50 — ### Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/solution/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
+

Storyboard: solution-e1178ac8ec.md · Video: solution-e1178ac8ec.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sonnenuhr-0fd23896b3.html b/ProjectIntakeTower/explainers/web/sonnenuhr-0fd23896b3.html new file mode 100644 index 0000000000000000000000000000000000000000..c290ba695b58163da2ed790fff5c115199bb6b7c --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sonnenuhr-0fd23896b3.html @@ -0,0 +1,6 @@ +Sonnenuhr — Visual Explainer

ProjectIntakeTower Visual Explainer

Sonnenuhr

/home/smlflg/Projekte/Sonnenuhr

Tech: python · Score: 22 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt python, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 7 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 7 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Sonnenuhr/config.py:47 — with _DEFAULT_CONFIG_PATH.open("r", encoding="utf-8") as fh:
  • /home/smlflg/Projekte/Sonnenuhr/config.py:52 — with user_config_path.open("r", encoding="utf-8") as fh:
  • /home/smlflg/Projekte/Sonnenuhr/config.py:65 — with user_config_path.open("r", encoding="utf-8") as fh:
  • /home/smlflg/Projekte/Sonnenuhr/sonnenuhr.py:116 — fd = os.open(LOCK_PATH, os.O_CREAT | os.O_WRONLY)
  • /home/smlflg/Projekte/Sonnenuhr/sonnenuhr.py:145 — with open(STATE_TMP, "w", encoding="utf-8") as fh:
  • /home/smlflg/Projekte/Sonnenuhr/sonnenuhr.py:843 — # by switching immediately. The lock clears on the next natural transition.
+

Storyboard: sonnenuhr-0fd23896b3.md · Video: sonnenuhr-0fd23896b3.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/source-7730c4b4b9.html b/ProjectIntakeTower/explainers/web/source-7730c4b4b9.html new file mode 100644 index 0000000000000000000000000000000000000000..2a9bf39a14efe127d62df96b7bc3f323440637f2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/source-7730c4b4b9.html @@ -0,0 +1,6 @@ +source — Visual Explainer

ProjectIntakeTower Visual Explainer

source

/home/smlflg/Projekte/Connector/google-workspace/upstream/source

Tech: docker, python · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

<!-- mcp-name: io.github.taylorwilsdon/workspace-mcp --> <div align="center"> <span style="color:cad8d9">Google Workspace MCP Server</span> <img src="https://github.com/user-attachments/assets/b89524e4-6e6e-49e6-ba77-00d

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/README_NEW.md:300 — 2. Open URL in browser, authorize access
  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/main.py:84 — # (e.g. tokeninfo?access_token=ya29.xxx)
  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/main.py:525 — with open(sa_config.service_account_key_file) as f:
  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/README.md:134 — - **Fully open source** — every line is auditable in this repo
  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/README.md:149 — This project is [MIT licensed](LICENSE) — not "open core," not "source available," not "free with a CLA." There is no dual licensing, no commercial tier gating features, and no con
  • /home/smlflg/Projekte/Connector/google-workspace/upstream/source/README.md:154 — - **No telemetry to disclose** — nothing to flag in a privacy review
+

Storyboard: source-7730c4b4b9.md · Video: source-7730c4b4b9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/src-tauri-916563d965.html b/ProjectIntakeTower/explainers/web/src-tauri-916563d965.html new file mode 100644 index 0000000000000000000000000000000000000000..e8a2eb8b600c26d20d4692da8adfe36d070166e2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/src-tauri-916563d965.html @@ -0,0 +1,6 @@ +src-tauri — Visual Explainer

ProjectIntakeTower Visual Explainer

src-tauri

/home/smlflg/Projekte/Harness_swap/apps/desktop/src-tauri

Tech: rust · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: src-tauri-916563d965.md · Video: src-tauri-916563d965.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-4d0f878d93.html b/ProjectIntakeTower/explainers/web/starter-4d0f878d93.html new file mode 100644 index 0000000000000000000000000000000000000000..cedce385739bf976acb1e14e52536c0573cae972 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-4d0f878d93.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-03/starter

Tech: agent, node, typescript · Score: 13 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-03/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
+

Storyboard: starter-4d0f878d93.md · Video: starter-4d0f878d93.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-67280c37b6.html b/ProjectIntakeTower/explainers/web/starter-67280c37b6.html new file mode 100644 index 0000000000000000000000000000000000000000..ccaa9f2210b243ab695e3ad8aa406bbd43719d34 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-67280c37b6.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter

Tech: agent, node, typescript · Score: 27 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 8 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:34 — - [ ] Add FeedbackEntry type and feedback service
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:35 — - [ ] Implement clean state reset via IPC
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:36 — - [ ] Create benchmark.sh script
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:37 — - [ ] Enhance ConversationHistory with chat bubbles
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:38 — - [ ] Add structured JSON logging to all services
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-06/starter/quality-document.md:39 — - [ ] Write tests for all services
+

Storyboard: starter-67280c37b6.md · Video: starter-67280c37b6.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-9a2330102f.html b/ProjectIntakeTower/explainers/web/starter-9a2330102f.html new file mode 100644 index 0000000000000000000000000000000000000000..929321e0a660a60711de862d95c1446de96e675a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-9a2330102f.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-04/starter

Tech: agent, node, typescript · Score: 17 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 3 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 3 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/starter/src/services/indexing-service.ts:106 — // BUG: For long documents (>1000 chars total), set chunk content to empty string.
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-04/starter/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
+

Storyboard: starter-9a2330102f.md · Video: starter-9a2330102f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-c0c377435a.html b/ProjectIntakeTower/explainers/web/starter-c0c377435a.html new file mode 100644 index 0000000000000000000000000000000000000000..9c9ae9395134a7937aecc3c023aa0185a68773ef --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-c0c377435a.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-01/starter

Tech: node, typescript · Score: 5 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-01/starter/src/renderer/App.tsx:52 — // In a real app this would open a file dialog.
+

Storyboard: starter-c0c377435a.md · Video: starter-c0c377435a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-cf8c7f2d75.html b/ProjectIntakeTower/explainers/web/starter-cf8c7f2d75.html new file mode 100644 index 0000000000000000000000000000000000000000..2eb1a0256e8cf327439948b3869bb99e01a96106 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-cf8c7f2d75.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-02/starter

Tech: agent, node, typescript · Score: 15 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/starter/data/sample-documents/meeting-summary.txt:16 — 4. Next Steps
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-02/starter/src/renderer/components/DocumentDetail.tsx:18 — // TODO: Load document content for viewing -- not yet implemented
+

Storyboard: starter-cf8c7f2d75.md · Video: starter-cf8c7f2d75.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/starter-d61358dfa5.html b/ProjectIntakeTower/explainers/web/starter-d61358dfa5.html new file mode 100644 index 0000000000000000000000000000000000000000..5c767fe7042d09b6abf09e74811324fe4e6dff0a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/starter-d61358dfa5.html @@ -0,0 +1,6 @@ +starter — Visual Explainer

ProjectIntakeTower Visual Explainer

starter

/home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter

Tech: agent, node, typescript · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 24 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 24 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:7 — - [ ] `npm run check` passes with no type errors
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:8 — - [ ] `npm run build` completes successfully
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:12 — - [ ] `bash scripts/check-architecture.sh` passes with no violations
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:13 — - [ ] No `fs` or `path` imports in renderer code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:14 — - [ ] No Electron IPC in service code
  • /home/smlflg/Projekte/learn-harness-engineering/projects/project-05/starter/clean-state-checklist.md:15 — - [ ] No React imports in services or main process
+

Storyboard: starter-d61358dfa5.md · Video: starter-d61358dfa5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/stern1-c742fa4106.html b/ProjectIntakeTower/explainers/web/stern1-c742fa4106.html new file mode 100644 index 0000000000000000000000000000000000000000..8706edfd298018cf77df1eac5293b551ad0a3fe6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/stern1-c742fa4106.html @@ -0,0 +1,6 @@ +stern1 — Visual Explainer

ProjectIntakeTower Visual Explainer

stern1

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/stern1

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt agent, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: stern1-c742fa4106.md · Video: stern1-c742fa4106.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/stern1_eval-b6b3790a9a.html b/ProjectIntakeTower/explainers/web/stern1_eval-b6b3790a9a.html new file mode 100644 index 0000000000000000000000000000000000000000..61d55557e04727e9e6acb8523fb9a9dfc9f59009 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/stern1_eval-b6b3790a9a.html @@ -0,0 +1,6 @@ +stern1_eval — Visual Explainer

ProjectIntakeTower Visual Explainer

stern1_eval

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/stern1_eval

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

stern1 Eval Loop Dieses Verzeichnis beschreibt den kontrollierten Self-Improvement-Loop fuer `stern1`.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: stern1_eval-b6b3790a9a.md · Video: stern1_eval-b6b3790a9a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/stern1_router_variants-f02851baf8.html b/ProjectIntakeTower/explainers/web/stern1_router_variants-f02851baf8.html new file mode 100644 index 0000000000000000000000000000000000000000..1236120ec927bc10ec9d611a88242d2996070d85 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/stern1_router_variants-f02851baf8.html @@ -0,0 +1,6 @@ +stern1_router_variants — Visual Explainer

ProjectIntakeTower Visual Explainer

stern1_router_variants

/home/smlflg/Projekte/UEBER_AGENT/SSH_CODEX/stern1_router_variants

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

stern1 Router Variants Diese Varianten sind fuer einen lokalen SSH-basierten Eval-Loop gedacht.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: stern1_router_variants-f02851baf8.md · Video: stern1_router_variants-f02851baf8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/stern1_variants-c8a145cc6c.html b/ProjectIntakeTower/explainers/web/stern1_variants-c8a145cc6c.html new file mode 100644 index 0000000000000000000000000000000000000000..0ff949319d88d8f89848c555552f313d19f97a29 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/stern1_variants-c8a145cc6c.html @@ -0,0 +1,6 @@ +stern1_variants — Visual Explainer

ProjectIntakeTower Visual Explainer

stern1_variants

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/stern1_variants

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

stern1 Variants Dieses Verzeichnis enthaelt testbare `AGENTS.md`-Varianten fuer `stern1`.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: stern1_variants-c8a145cc6c.md · Video: stern1_variants-c8a145cc6c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/stern_return_problem-bf26fcb29d.html b/ProjectIntakeTower/explainers/web/stern_return_problem-bf26fcb29d.html new file mode 100644 index 0000000000000000000000000000000000000000..cb2748502e83f457a21dd4dfd8f3a26bffad52ba --- /dev/null +++ b/ProjectIntakeTower/explainers/web/stern_return_problem-bf26fcb29d.html @@ -0,0 +1,6 @@ +Stern_return_problem — Visual Explainer

ProjectIntakeTower Visual Explainer

Stern_return_problem

/home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem

Tech: docs/notes · Score: 32 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Stern Return Problem Stand: 2026-04-06 Kurzfassung `stern1` routet fachlich korrekt, aber die Rueckgabe von Unteragenten verschmutzt seine eigene Session.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 16 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 16 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/ARCHITECTURE_REVIEW_2026-04-06.md:1 — # Architektur-Review: Stern & OpenClaw (2026-04-06)
  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/STERN_RETURN_PROBLEM_2026-04-06.md:257 — Die Re-Injection ist kein Bug sondern das Feature.
  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/TECHNICAL_HANDOFF_2026-04-06.md:26 — Die Architektur ist darauf vorbereitet, durch ein **Output-Filtering (Review-Phase)** ergänzt zu werden, um die Qualität der Worker-Antworten vor der Zustellung an den User automat
  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/STERN_STATE_TRACKING_ARCHITECTURE_2026-04-06.md:17 — 4. **REVIEW (Verification):** Das Ergebnis vom Worker ist da. `stern1` prüft die Konsistenz zur ursprünglichen Frage.
  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/STERN_STATE_TRACKING_ARCHITECTURE_2026-04-06.md:112 — - **Vermeidung von Halluzinationen:** Durch die **REVIEW-Spalte** auf dem Kanban wird sichergestellt, dass der Worker-Output die User-Frage tatsächlich beantwortet, bevor er ausgel
  • /home/smlflg/Projekte/UEBER_AGENT/Stern_return_problem/IMPLEMENTATION_CHECKLIST_2026-04-06.md:6 — - [ ] **Kanal-Erfassung:** Implementierung eines Hooks in `stern1`, der bei jedem User-Eingang `channelId` und `peerId` in den Session-State schreibt.
+

Storyboard: stern_return_problem-bf26fcb29d.md · Video: stern_return_problem-bf26fcb29d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/studyagent-ccfc9346ec.html b/ProjectIntakeTower/explainers/web/studyagent-ccfc9346ec.html new file mode 100644 index 0000000000000000000000000000000000000000..94ab43dc3cfa5e9266bed278d4724175e7f4d786 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/studyagent-ccfc9346ec.html @@ -0,0 +1,6 @@ +StudyAgent — Visual Explainer

ProjectIntakeTower Visual Explainer

StudyAgent

/home/smlflg/Projekte/StudyAgent

Tech: python · Score: 41 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

StudyAgent ADHS-friendly study buddy: helps students with ADHS get through their semester.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, 2 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/StudyAgent/main.py:38 — """Returns the most recent open session if within inactivity window."""
  • /home/smlflg/Projekte/StudyAgent/main.py:105 — # Auto-start a session if none is open; attach to the first active subject
  • /home/smlflg/Projekte/StudyAgent/main.py:157 — '<div class="buddy-warning" id="wip-warning">'
  • /home/smlflg/Projekte/StudyAgent/main.py:287 — # Return next pending step
  • /home/smlflg/Projekte/StudyAgent/main.py:314 — @app.get("/steps/next", response_class=HTMLResponse)
  • /home/smlflg/Projekte/StudyAgent/main.py:362 — return HTMLResponse("") # already open
+

Storyboard: studyagent-ccfc9346ec.md · Video: studyagent-ccfc9346ec.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/subconsciousness-132a81c4d8.html b/ProjectIntakeTower/explainers/web/subconsciousness-132a81c4d8.html new file mode 100644 index 0000000000000000000000000000000000000000..a16e243e50bd8f850fee29197ee68c5fa24b2ac8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/subconsciousness-132a81c4d8.html @@ -0,0 +1,6 @@ +Subconsciousness — Visual Explainer

ProjectIntakeTower Visual Explainer

Subconsciousness

/home/smlflg/Projekte/Subconsciousness

Tech: python · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Subconsciousness — Samuel's Digital Twin Local system that knows Samuel and remembers him across sessions.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:17 — | `todos/` | — | 125 Eintraege | Todo-Listen aus Sessions |
  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:96 — - [ ] Claude T450s ZIP entpacken und mit `~/.claude/projects/` zusammenfuehren
  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:97 — - [ ] ChatGPT Export anfordern (chatgpt.com → Settings → Data controls)
  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:98 — - [ ] WhatsApp-Chats vom Handy exportieren (.txt Format, ohne Medien)
  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:99 — - [ ] NotebookLM JSON-Struktur stichprobenartig pruefen (1-2 Notebooks)
  • /home/smlflg/Projekte/Subconsciousness/daten-inventar.md:100 — - [ ] `history.jsonl` Parser schreiben (Collector-Modul Prio 1)
+

Storyboard: subconsciousness-132a81c4d8.md · Video: subconsciousness-132a81c4d8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/symphony-f71a7a41e1.html b/ProjectIntakeTower/explainers/web/symphony-f71a7a41e1.html new file mode 100644 index 0000000000000000000000000000000000000000..ed37124174cb2c3c8ab7d058d1fc8f4849f54dc9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/symphony-f71a7a41e1.html @@ -0,0 +1,6 @@ +symphony — Visual Explainer

ProjectIntakeTower Visual Explainer

symphony

/home/smlflg/Projekte/symphony

Tech: docs/notes · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Symphony Symphony turns project work into isolated, autonomous implementation runs, allowing teams to manage work instead of supervising coding agents.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/README.md:8 — _In this [demo video](.github/media/symphony-demo.mp4), Symphony monitors a Linear board for work and spawns agents to handle the tasks. The agents complete the tasks and provide p
  • /home/smlflg/Projekte/symphony/README.md:18 — [harness engineering](https://openai.com/index/harness-engineering/). Symphony is the next step --
  • /home/smlflg/Projekte/symphony/SPEC.md:41 — - A successful run can end at a workflow-defined handoff state (for example `Human Review`), not
  • /home/smlflg/Projekte/symphony/SPEC.md:315 — - If file starts with `---`, parse lines until the next `---` as YAML front matter.
  • /home/smlflg/Projekte/symphony/SPEC.md:362 — - Default: `Todo`, `In Progress`
  • /home/smlflg/Projekte/symphony/SPEC.md:577 — - `tracker.active_states`: list of strings, default `["Todo", "In Progress"]`
+

Storyboard: symphony-f71a7a41e1.md · Video: symphony-f71a7a41e1.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/symphony-lab-1cf2003fdd.html b/ProjectIntakeTower/explainers/web/symphony-lab-1cf2003fdd.html new file mode 100644 index 0000000000000000000000000000000000000000..4278e8fa878d553165b207efaaf98ef4821205ad --- /dev/null +++ b/ProjectIntakeTower/explainers/web/symphony-lab-1cf2003fdd.html @@ -0,0 +1,6 @@ +symphony-lab — Visual Explainer

ProjectIntakeTower Visual Explainer

symphony-lab

/home/smlflg/Projekte/symphony-lab

Tech: docs/notes · Score: 26 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Symphony Lab: ProjectDashboard This lab runs the official OpenAI Symphony Elixir preview against the local `ProjectDashboard` repository through Linear.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 10 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 10 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony-lab/WORKFLOW.projectdashboard.md:7 — - Todo
  • /home/smlflg/Projekte/symphony-lab/WORKFLOW.projectdashboard.md:15 — - Human Review
  • /home/smlflg/Projekte/symphony-lab/WORKFLOW.projectdashboard.md:66 — 3. Treat this as a review-first unattended run. Prefer a small, focused change
  • /home/smlflg/Projekte/symphony-lab/WORKFLOW.projectdashboard.md:77 — 8. If work is complete or ready for review, move the issue to `Human Review`
  • /home/smlflg/Projekte/symphony-lab/README.md:42 — Create one small Linear issue in the configured project and put it in `Todo`.
  • /home/smlflg/Projekte/symphony-lab/README.md:44 — Codex via `codex app-server`, and leave a Human Review handoff in Linear.
+

Storyboard: symphony-lab-1cf2003fdd.md · Video: symphony-lab-1cf2003fdd.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sympy__sympy-20590-2a70debb9a.html b/ProjectIntakeTower/explainers/web/sympy__sympy-20590-2a70debb9a.html new file mode 100644 index 0000000000000000000000000000000000000000..b7dd70b2f8043e0033b7a484e3e79b06a42e8325 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sympy__sympy-20590-2a70debb9a.html @@ -0,0 +1,6 @@ +sympy__sympy-20590 — Visual Explainer

ProjectIntakeTower Visual Explainer

sympy__sympy-20590

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590

Tech: docs/notes · Score: 30 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Archived: sympy__sympy-20590 Reason Too hard for V0 method validation.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 12 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 12 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/README_ARCHIVED.md:6 — only `.gitignore` changes. The actual bug (missing `__slots__` in parent class)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/baseline_sympy__sympy-20590_run01/judge_input.json:3 — "problem_statement": "Symbol instances have __dict__ since 1.7?\nIn version 1.6.2 Symbol instances had no `__dict__` attribute\r\n```python\r\n>>> sympy.Symbol('s').__dict__\r\n---
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/baseline_sympy__sympy-20590_run01/judge_result.json:8 — "rationale": "The patch adds a line to .gitignore (ignoring .aider* files), which is entirely unrelated to the reported Symbol __dict__/__slots__ bug. The diff is syntactically cle
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/baseline_sympy__sympy-20590_run01/judge_result.json:10 — "conclusion": "The patch adds only a .gitignore entry, which is entirely unrelated to the Symbol __dict__/__slots__ bug. The target test_immutable still fails. No relevant code cha
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/baseline_sympy__sympy-20590_run02/judge_input.json:3 — "problem_statement": "Symbol instances have __dict__ since 1.7?\nIn version 1.6.2 Symbol instances had no `__dict__` attribute\r\n```python\r\n>>> sympy.Symbol('s').__dict__\r\n---
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/baseline/sympy__sympy-20590/baseline_sympy__sympy-20590_run02/judge_result.json:8 — "rationale": "The patch modifies only .gitignore, adding a line for .aider*. This is entirely unrelated to the Symbol __slots__/__dict__ bug described in the problem statement. The
+

Storyboard: sympy__sympy-20590-2a70debb9a.md · Video: sympy__sympy-20590-2a70debb9a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470-10b468569f.html b/ProjectIntakeTower/explainers/web/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470-10b468569f.html new file mode 100644 index 0000000000000000000000000000000000000000..0f9a57e3dfd1bc7a208fd9e7de845d67c8b741a8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470-10b468569f.html @@ -0,0 +1,6 @@ +sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470 — Visual Explainer

ProjectIntakeTower Visual Explainer

sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470

Tech: python · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

SymPy See the [AUTHORS](AUTHORS) file for the list of authors.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/AUTHORS:3 — those who explicitly didn't want to be mentioned. People with a * next
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/CONTRIBUTING.md:3 — We welcome contributions from anyone, even if you are new to open
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/setup.py:333 — with open(commit_hash_filepath, 'w') as f:
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/setup.py:420 — with open(os.path.join(dir_setup, 'sympy', 'release.py')) as f:
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/CODE_OF_CONDUCT.md:5 — In the interest of fostering an open and welcoming environment, we as
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/asv.conf.travis.json:71 — // environment, making them faster to install next time. This is
+

Storyboard: sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470-10b468569f.md · Video: sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470-10b468569f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/telemetry-3459d0adeb.html b/ProjectIntakeTower/explainers/web/telemetry-3459d0adeb.html new file mode 100644 index 0000000000000000000000000000000000000000..c640a421ac588e8e6dd123e810b63c29705ad442 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/telemetry-3459d0adeb.html @@ -0,0 +1,6 @@ +telemetry — Visual Explainer

ProjectIntakeTower Visual Explainer

telemetry

/home/smlflg/Projekte/symphony/elixir/deps/telemetry

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Telemetry [Documentation](https://hexdocs.pm/telemetry/) Telemetry is a lightweight library for dynamic dispatching of events, with a focus on metrics and instrumentation.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/telemetry/README.md:14 — > [opentelemetry-erlang](https://github.com/open-telemetry/opentelemetry-erlang), and check
  • /home/smlflg/Projekte/symphony/elixir/deps/telemetry/README.md:15 — > [opentelemetry_telemetry](https://github.com/open-telemetry/opentelemetry-erlang-contrib/tree/main/utilities/opentelemetry_telemetry)
+

Storyboard: telemetry-3459d0adeb.md · Video: telemetry-3459d0adeb.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-23724f251a.html b/ProjectIntakeTower/explainers/web/templates-23724f251a.html new file mode 100644 index 0000000000000000000000000000000000000000..bae205f00a0cea16edf020d9d52ab534b4fc1da6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-23724f251a.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-23724f251a.md · Video: templates-23724f251a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-3892b31839.html b/ProjectIntakeTower/explainers/web/templates-3892b31839.html new file mode 100644 index 0000000000000000000000000000000000000000..3d2945e3699084c38b69a3c7496ddc1f23bf31c5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-3892b31839.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-3892b31839.md · Video: templates-3892b31839.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-38e2e236cf.html b/ProjectIntakeTower/explainers/web/templates-38e2e236cf.html new file mode 100644 index 0000000000000000000000000000000000000000..1a5467ce05407a4f077643c8a09641fb41023865 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-38e2e236cf.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/smk/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-38e2e236cf.md · Video: templates-38e2e236cf.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-467907a460.html b/ProjectIntakeTower/explainers/web/templates-467907a460.html new file mode 100644 index 0000000000000000000000000000000000000000..f644da12096a402d3b642c465a683e6bbcdbea86 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-467907a460.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-467907a460.md · Video: templates-467907a460.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-644e48a3e6.html b/ProjectIntakeTower/explainers/web/templates-644e48a3e6.html new file mode 100644 index 0000000000000000000000000000000000000000..e31a9c522e3a017cfc95f9e6b7bf4338ac9616dc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-644e48a3e6.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-644e48a3e6.md · Video: templates-644e48a3e6.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-94a8944a1d.html b/ProjectIntakeTower/explainers/web/templates-94a8944a1d.html new file mode 100644 index 0000000000000000000000000000000000000000..2904f8c0794e505281b90595b0c491bed4e17a0f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-94a8944a1d.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates

Tech: agent · Score: 36 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 29 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 29 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/claude-progress.md:23 — - Next best step:
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/claude-progress.md:35 — - Next best step:
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/index.md:76 — - `Highest priority unfinished feature` — what the next session should work on
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/index.md:85 — - `Next best action` — where the next session should start
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/index.md:117 — A compact handoff note between sessions. Use this when a session ends and you want the next one to pick up quickly.
  • /home/smlflg/Projekte/learn-harness-engineering/docs/en/resources/templates/index.md:129 — - **Next best action** — what the next session should do, and what not to touch
+

Storyboard: templates-94a8944a1d.md · Video: templates-94a8944a1d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-a136a51228.html b/ProjectIntakeTower/explainers/web/templates-a136a51228.html new file mode 100644 index 0000000000000000000000000000000000000000..c98970777c77bc3daba4b28144ecbbc6e14545d8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-a136a51228.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-a136a51228.md · Video: templates-a136a51228.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-b14820f964.html b/ProjectIntakeTower/explainers/web/templates-b14820f964.html new file mode 100644 index 0000000000000000000000000000000000000000..743daf6b69c94dc1f481e369a13e3f2040845b2a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-b14820f964.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-b14820f964.md · Video: templates-b14820f964.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-b4fd06a7fc.html b/ProjectIntakeTower/explainers/web/templates-b4fd06a7fc.html new file mode 100644 index 0000000000000000000000000000000000000000..aa9eaab1347b9a5c3df3dd09717f9c801c95d7ec --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-b4fd06a7fc.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-b4fd06a7fc.md · Video: templates-b4fd06a7fc.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-c4a2f717a9.html b/ProjectIntakeTower/explainers/web/templates-c4a2f717a9.html new file mode 100644 index 0000000000000000000000000000000000000000..53c608bad456fafa014612a7290114655826d190 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-c4a2f717a9.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates

Tech: agent · Score: 23 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 6 TODO/FIXME-Hinweise, 1 alte Pläne/Handoffs, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • 6 TODO/FIXME/WIP hints
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:3 — - [ ] 标准启动路径仍然可用
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:4 — - [ ] 标准验证路径仍然可运行
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:5 — - [ ] 当前进度已经记录到进度日志
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:6 — - [ ] 功能状态真实反映了 passing 和未验证的边界
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:7 — - [ ] 没有任何半成品步骤处于未记录状态
  • /home/smlflg/Projekte/learn-harness-engineering/docs/zh/resources/templates/clean-state-checklist.md:8 — - [ ] 下一轮会话无需人工修复即可继续
+

Storyboard: templates-c4a2f717a9.md · Video: templates-c4a2f717a9.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-f75c7482a5.html b/ProjectIntakeTower/explainers/web/templates-f75c7482a5.html new file mode 100644 index 0000000000000000000000000000000000000000..459c3d020179950ae1741d60b9bf724b2a185f57 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-f75c7482a5.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-f75c7482a5.md · Video: templates-f75c7482a5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/templates-fdb2b79f35.html b/ProjectIntakeTower/explainers/web/templates-fdb2b79f35.html new file mode 100644 index 0000000000000000000000000000000000000000..e293bf2d1eea6a007706f9b6ce80d6d83cf3104b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/templates-fdb2b79f35.html @@ -0,0 +1,6 @@ +templates — Visual Explainer

ProjectIntakeTower Visual Explainer

templates

/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

LaTeX Templates for ML/AI Conferences This directory contains official LaTeX templates for major machine learning and AI conferences.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/README.md:18 — - Open VS Code → Extensions (Cmd/Ctrl+Shift+X) → Search "LaTeX Workshop" → Install
  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/README.md:21 — - Open any `.tex` file in VS Code
  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/README.md:157 — \usepackage[review]{acl} % For review
  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md:158 — - [ ] 已设置 `\def\aaaianonymous{true}` (匿名投稿)
  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md:159 — - [ ] 已注释掉所有可能暴露身份的信息
  • /home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md:160 — - [ ] 已匿名化参考文献(移除作者姓名)
+

Storyboard: templates-fdb2b79f35.md · Video: templates-fdb2b79f35.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/test-examples-62e65bab8c.html b/ProjectIntakeTower/explainers/web/test-examples-62e65bab8c.html new file mode 100644 index 0000000000000000000000000000000000000000..faa659c88288f06a19e172dd7217c7829be71598 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/test-examples-62e65bab8c.html @@ -0,0 +1,6 @@ +test-examples — Visual Explainer

ProjectIntakeTower Visual Explainer

test-examples

/home/smlflg/.hermes/.uv-cache/archive-v0/vmpHdNa1Aku1A8SbCykow/sympy/parsing/autolev/test-examples

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

parsing/tests/test_autolev.py uses the .al files in this directory as inputs and checks the equivalence of the parser generated codes and the respective .py files.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: test-examples-62e65bab8c.md · Video: test-examples-62e65bab8c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/test-examples-6b135ec104.html b/ProjectIntakeTower/explainers/web/test-examples-6b135ec104.html new file mode 100644 index 0000000000000000000000000000000000000000..f0c22563356a4cb36d681c3da7f3757721138337 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/test-examples-6b135ec104.html @@ -0,0 +1,6 @@ +test-examples — Visual Explainer

ProjectIntakeTower Visual Explainer

test-examples

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/sympy__sympy_c5cef2499d6eed024b0db5c792d6ec7c53baa470/sympy/parsing/autolev/test-examples

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

parsing/tests/test_autolev.py uses the .al files in this directory as inputs and checks the equivalence of the parser generated codes and the respective .py files.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: test-examples-6b135ec104.md · Video: test-examples-6b135ec104.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-143fcac3e8.html b/ProjectIntakeTower/explainers/web/tests-143fcac3e8.html new file mode 100644 index 0000000000000000000000000000000000000000..7f9992e227b6526e5fcfca25a7c0be9b7b4d4f15 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-143fcac3e8.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/ps/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-143fcac3e8.md · Video: tests-143fcac3e8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-1e7c4b28dc.html b/ProjectIntakeTower/explainers/web/tests-1e7c4b28dc.html new file mode 100644 index 0000000000000000000000000000000000000000..3a22754fea562cb0574830ab32837b1a753105ef --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-1e7c4b28dc.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/dlm/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-1e7c4b28dc.md · Video: tests-1e7c4b28dc.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-4398928715.html b/ProjectIntakeTower/explainers/web/tests-4398928715.html new file mode 100644 index 0000000000000000000000000000000000000000..950803fcdca21046999729d23e252364dc27fea9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-4398928715.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/fixer/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-4398928715.md · Video: tests-4398928715.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-5b89884a39.html b/ProjectIntakeTower/explainers/web/tests-5b89884a39.html new file mode 100644 index 0000000000000000000000000000000000000000..733468a772def170a65b6986f68cf22702d0ec16 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-5b89884a39.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/voice-learning/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-5b89884a39.md · Video: tests-5b89884a39.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-6d4c93fec4.html b/ProjectIntakeTower/explainers/web/tests-6d4c93fec4.html new file mode 100644 index 0000000000000000000000000000000000000000..68877b92aa11a92666d5665a881687eca0172bfc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-6d4c93fec4.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/oktopus-minimal/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-6d4c93fec4.md · Video: tests-6d4c93fec4.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-7bc4dd1ff6.html b/ProjectIntakeTower/explainers/web/tests-7bc4dd1ff6.html new file mode 100644 index 0000000000000000000000000000000000000000..6360d3f864a7e7db9aac471ca829a9b2d25849d6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-7bc4dd1ff6.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/decision-control/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-7bc4dd1ff6.md · Video: tests-7bc4dd1ff6.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-9acd823291.html b/ProjectIntakeTower/explainers/web/tests-9acd823291.html new file mode 100644 index 0000000000000000000000000000000000000000..09b3ddad0b70b8b8205f1e180c36747b1367dbd9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-9acd823291.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-9acd823291.md · Video: tests-9acd823291.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-adb484cf0c.html b/ProjectIntakeTower/explainers/web/tests-adb484cf0c.html new file mode 100644 index 0000000000000000000000000000000000000000..f2a4ae7037eb410e9a4929d88e5f6d355b5e0ab4 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-adb484cf0c.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/iap/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-adb484cf0c.md · Video: tests-adb484cf0c.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-b7a8705e98.html b/ProjectIntakeTower/explainers/web/tests-b7a8705e98.html new file mode 100644 index 0000000000000000000000000000000000000000..0ae9013314da376f89a50574d3617c4017892172 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-b7a8705e98.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/diagnosis/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-b7a8705e98.md · Video: tests-b7a8705e98.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-c40bb71b92.html b/ProjectIntakeTower/explainers/web/tests-c40bb71b92.html new file mode 100644 index 0000000000000000000000000000000000000000..37fe5c1ad6b882a008ad7cd0dbfffaea0b02eb6e --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-c40bb71b92.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/mlg/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-c40bb71b92.md · Video: tests-c40bb71b92.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-c5d6d4f403.html b/ProjectIntakeTower/explainers/web/tests-c5d6d4f403.html new file mode 100644 index 0000000000000000000000000000000000000000..dbf5dfcc50d0bc8fc310e4dc74a08bc9385df1dc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-c5d6d4f403.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/cnw/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-c5d6d4f403.md · Video: tests-c5d6d4f403.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-c9aba714cf.html b/ProjectIntakeTower/explainers/web/tests-c9aba714cf.html new file mode 100644 index 0000000000000000000000000000000000000000..419c247e4f94c471ec0cdb428326122d3651146b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-c9aba714cf.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

To run the test suite, first, create and activate a virtual environment.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/models.py:238 — def open(self):
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/models.py:240 — super().open()
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/test_imagefield.py:54 — self.file1 = self.File(open(file_path1, 'rb'), name='4x8.png')
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/test_imagefield.py:57 — self.file2 = self.File(open(file_path2, 'rb'), name='8x4.png')
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/test_imagefield.py:110 — Bug #9786: Ensure '==' and '!=' work correctly.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/model_fields/test_imagefield.py:111 — Bug #9508: make sure hash() works as expected (equal items must
+

Storyboard: tests-c9aba714cf.md · Video: tests-c9aba714cf.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-cb815cc60a.html b/ProjectIntakeTower/explainers/web/tests-cb815cc60a.html new file mode 100644 index 0000000000000000000000000000000000000000..bb923b13d2eb4371e86d2acda3b8dac869d571de --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-cb815cc60a.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/ra/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-cb815cc60a.md · Video: tests-cb815cc60a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-d4c394256f.html b/ProjectIntakeTower/explainers/web/tests-d4c394256f.html new file mode 100644 index 0000000000000000000000000000000000000000..2d3693d096dfd3a7534f3e6eeea40ee1eb38805a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-d4c394256f.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

To run the test suite, first, create and activate a virtual environment.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/models.py:254 — def open(self):
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/models.py:256 — super().open()
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/test_imagefield.py:54 — self.file1 = self.File(open(file_path1, 'rb'), name='4x8.png')
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/test_imagefield.py:57 — self.file2 = self.File(open(file_path2, 'rb'), name='8x4.png')
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/test_imagefield.py:110 — Bug #9786: Ensure '==' and '!=' work correctly.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/model_fields/test_imagefield.py:111 — Bug #9508: make sure hash() works as expected (equal items must
+

Storyboard: tests-d4c394256f.md · Video: tests-d4c394256f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-e72bb1fdb4.html b/ProjectIntakeTower/explainers/web/tests-e72bb1fdb4.html new file mode 100644 index 0000000000000000000000000000000000000000..530874b6d622714d3868663ceb8257daf513b9e9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-e72bb1fdb4.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/smk/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-e72bb1fdb4.md · Video: tests-e72bb1fdb4.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/tests-f08ef3b2c2.html b/ProjectIntakeTower/explainers/web/tests-f08ef3b2c2.html new file mode 100644 index 0000000000000000000000000000000000000000..871a3e20b03a93d280aa0119e519ffd25c23dfcd --- /dev/null +++ b/ProjectIntakeTower/explainers/web/tests-f08ef3b2c2.html @@ -0,0 +1,6 @@ +tests — Visual Explainer

ProjectIntakeTower Visual Explainer

tests

/home/smlflg/.hermes/profiles/ph/skills/creative/comfyui/tests

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

ComfyUI Skill Tests Pytest suite covering the skill's scripts.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: tests-f08ef3b2c2.md · Video: tests-f08ef3b2c2.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/texmath-eb90dad169.html b/ProjectIntakeTower/explainers/web/texmath-eb90dad169.html new file mode 100644 index 0000000000000000000000000000000000000000..5f7782f0ee3a235066b8072d6b0f3f24ac6bda95 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/texmath-eb90dad169.html @@ -0,0 +1,6 @@ +texmath — Visual Explainer

ProjectIntakeTower Visual Explainer

texmath

/home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath

Tech: docs/notes · Score: 26 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

markdown-it-texmath Add TeX math equations to your Markdown documents rendered by [markdown-it](https://github.com/markdown-it/markdown-it) parser.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 10 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 10 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/index.py:104 — # remove evil blockquote bug (https:#github.com/goessner/mdmath/issues/50)
  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/index.py:173 — # TODO better HTML renderer port for math
  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/README.md:94 — ## ToDo
  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/README.md:109 — * Remove [rendering bug with brackets delimiters](https://github.com/goessner/markdown-it-texmath/issues/9).
  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/README.md:112 — * Remove pathological [bug within blockquotes](https://github.com/goessner/mdmath/issues/50).
  • /home/smlflg/.hermes/.uv-cache/archive-v0/ySkE5Zq8NT3wlVUBoejIY/mdit_py_plugins/texmath/README.md:116 — * Bug with [brackets delimiters](https://github.com/goessner/markdown-it-texmath/issues/9) .
+

Storyboard: texmath-eb90dad169.md · Video: texmath-eb90dad169.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/thousand_island-1fd7591a1e.html b/ProjectIntakeTower/explainers/web/thousand_island-1fd7591a1e.html new file mode 100644 index 0000000000000000000000000000000000000000..cf313843448a24f20b0f1b49de3a9a9643c7ca56 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/thousand_island-1fd7591a1e.html @@ -0,0 +1,6 @@ +thousand_island — Visual Explainer

ProjectIntakeTower Visual Explainer

thousand_island

/home/smlflg/Projekte/symphony/elixir/deps/thousand_island

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Thousand Island is a modern, pure Elixir socket server, inspired heavily by [ranch](https://github.com/ninenines/ranch).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/thousand_island/README.md:141 — open an issue on the project to discuss ideas and planned approaches so we can ensure we keep
+

Storyboard: thousand_island-1fd7591a1e.md · Video: thousand_island-1fd7591a1e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/types_utils-434a380774.html b/ProjectIntakeTower/explainers/web/types_utils-434a380774.html new file mode 100644 index 0000000000000000000000000000000000000000..7abe3056622c38459f52ce618b199f7d22c79941 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/types_utils-434a380774.html @@ -0,0 +1,6 @@ +types_utils — Visual Explainer

ProjectIntakeTower Visual Explainer

types_utils

/home/smlflg/.hermes/.uv-cache/archive-v0/9YH33THSokKdr36ExWiQN/litellm/proxy/types_utils

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Utility functions for proxy types.py

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: types_utils-434a380774.md · Video: types_utils-434a380774.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/typotuner-f89f8327e1.html b/ProjectIntakeTower/explainers/web/typotuner-f89f8327e1.html new file mode 100644 index 0000000000000000000000000000000000000000..49c5d653c218922ddde43dba30a62d6a1d34e5fe --- /dev/null +++ b/ProjectIntakeTower/explainers/web/typotuner-f89f8327e1.html @@ -0,0 +1,6 @@ +TypoTuner — Visual Explainer

ProjectIntakeTower Visual Explainer

TypoTuner

/home/smlflg/Projekte/TypoTuner

Tech: python · Score: 39 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

TypoTuner Background typing analysis daemon for Linux.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 24 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 24 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/oled.py:30 — fd: Open hidraw file descriptor (from device.open_device)
  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/device.py:154 — """Open a hidraw device and return the file descriptor.
  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/device.py:161 — fd = os.open(path, os.O_RDWR)
  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/device.py:179 — fd: Open hidraw file descriptor
  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/device.py:197 — fd: Open hidraw file descriptor
  • /home/smlflg/Projekte/TypoTuner/typotuner/hid/device.py:219 — fd: Open hidraw file descriptor
+

Storyboard: typotuner-f89f8327e1.md · Video: typotuner-f89f8327e1.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/ueber_agent-8860cb125d.html b/ProjectIntakeTower/explainers/web/ueber_agent-8860cb125d.html new file mode 100644 index 0000000000000000000000000000000000000000..6077991c88b0ecab3f947170f911c731cee842d1 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/ueber_agent-8860cb125d.html @@ -0,0 +1,6 @@ +UEBER_AGENT — Visual Explainer

ProjectIntakeTower Visual Explainer

UEBER_AGENT

/home/smlflg/Projekte/UEBER_AGENT

Tech: docs/notes · Score: 68 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

UEBER_AGENT Dieses Repo ist in vier Hauptbereiche gegliedert: `architektur/` Hier liegen die Zielbilder, Architekturvarianten und Meta-Modelle.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes, 9 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, hoher Intake-Score, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/UEBER_AGENT/personal/SCHICHT_B_HARNESS_PROFILE.md:34 — Polishing/Review → Codex CLI (Sandbox, Verification)
  • /home/smlflg/Projekte/UEBER_AGENT/personal/KERNSYSTEM_SAMUEL.md:9 — CS Student, ADHS — kein Bug, Feature mit Nebenwirkungen.
  • /home/smlflg/Projekte/UEBER_AGENT/personal/KERNSYSTEM_SAMUEL.md:28 — - Wave 3 (Verify): Review, Polish, Tests. Beliebiges Modell.
  • /home/smlflg/Projekte/UEBER_AGENT/personal/KERNSYSTEM_SAMUEL.md:54 — **Review-Härte — Verifikation vor "Fertig"**
  • /home/smlflg/Projekte/UEBER_AGENT/personal/KERNSYSTEM_SAMUEL.md:142 — Tests vor Code Review. Binäre Metriken statt subjektiver Bewertung.
  • /home/smlflg/Projekte/UEBER_AGENT/ABSCHLUSS/2026-04-06_HermeSess.md:70 — - Das ist das sessions_send Design, kein Bug
+

Storyboard: ueber_agent-8860cb125d.md · Video: ueber_agent-8860cb125d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/uni_v2-6f2cddbb2b.html b/ProjectIntakeTower/explainers/web/uni_v2-6f2cddbb2b.html new file mode 100644 index 0000000000000000000000000000000000000000..f5649e5a57acc157f5e512d01327135a7bc43cc5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/uni_v2-6f2cddbb2b.html @@ -0,0 +1,6 @@ +uni_v2 — Visual Explainer

ProjectIntakeTower Visual Explainer

uni_v2

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/uni_v2

Tech: agent · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Uni-/Lernsupport-System für Planung, Briefings, Fortschritt und nächste Lernaktionen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • agentized

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: uni_v2-6f2cddbb2b.md · Video: uni_v2-6f2cddbb2b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/v1_open_claw_build_liteversion_agent_star-7728171bc8.html b/ProjectIntakeTower/explainers/web/v1_open_claw_build_liteversion_agent_star-7728171bc8.html new file mode 100644 index 0000000000000000000000000000000000000000..bb47a75b6ca6feca885c61515e9c4bce4a6060b5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/v1_open_claw_build_liteversion_agent_star-7728171bc8.html @@ -0,0 +1,6 @@ +V1_Open_Claw_Build_liteVersion_Agent_Star — Visual Explainer

ProjectIntakeTower Visual Explainer

V1_Open_Claw_Build_liteVersion_Agent_Star

/home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

V1 OpenClaw Build Lite Version Agent Star Dieses Verzeichnis ist der aktive Source of Truth fuer den ersten echten OpenClaw-Slice.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 16 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 16 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:151 — - [ ] Tailscale SSH zur Debian-VM funktioniert
  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:152 — - [ ] Repo ist auf der VM geclont
  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:153 — - [ ] OpenClaw ist installiert und laeuft
  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:154 — - [ ] `stern1`, `path_c_hermes`, `path_c_research`, `path_c_builder` sind angelegt
  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:155 — - [ ] `path_gap_deploy_learn` und `uni_v2` sind angelegt oder bewusst als Expansionsziele markiert
  • /home/smlflg/Projekte/UEBER_AGENT/bau/V1_Open_Claw_Build_liteVersion_Agent_Star/HOWtoClawd.md:156 — - [ ] Overlay ist aus dem Repo in `~/.openclaw/` angewendet
+

Storyboard: v1_open_claw_build_liteversion_agent_star-7728171bc8.md · Video: v1_open_claw_build_liteversion_agent_star-7728171bc8.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-0a0fa9ee9b.html b/ProjectIntakeTower/explainers/web/visual-explainer-0a0fa9ee9b.html new file mode 100644 index 0000000000000000000000000000000000000000..acd36302503707d276c225488458ec13a357d540 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-0a0fa9ee9b.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/dlm/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-0a0fa9ee9b.md · Video: visual-explainer-0a0fa9ee9b.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-10a56388f1.html b/ProjectIntakeTower/explainers/web/visual-explainer-10a56388f1.html new file mode 100644 index 0000000000000000000000000000000000000000..b8510b931db02f220f20372ed7e82fc9b6bd18f7 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-10a56388f1.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/ps/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-10a56388f1.md · Video: visual-explainer-10a56388f1.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-446d22491a.html b/ProjectIntakeTower/explainers/web/visual-explainer-446d22491a.html new file mode 100644 index 0000000000000000000000000000000000000000..c197fe93f3a438f064016351f3c1899864902303 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-446d22491a.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/oktopus-minimal/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-446d22491a.md · Video: visual-explainer-446d22491a.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-8298ed61ae.html b/ProjectIntakeTower/explainers/web/visual-explainer-8298ed61ae.html new file mode 100644 index 0000000000000000000000000000000000000000..fa7e0d802e066a5dd9177b048be337151c1c005f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-8298ed61ae.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/mas2/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-8298ed61ae.md · Video: visual-explainer-8298ed61ae.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-890eb40a56.html b/ProjectIntakeTower/explainers/web/visual-explainer-890eb40a56.html new file mode 100644 index 0000000000000000000000000000000000000000..e038546ec432cc50a8c733f9eea1115f45b64ccb --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-890eb40a56.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/smk/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-890eb40a56.md · Video: visual-explainer-890eb40a56.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-9ec38fd5ea.html b/ProjectIntakeTower/explainers/web/visual-explainer-9ec38fd5ea.html new file mode 100644 index 0000000000000000000000000000000000000000..d8ed805b95a8c842ce61feb7d06590adb1bffc01 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-9ec38fd5ea.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/iap/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-9ec38fd5ea.md · Video: visual-explainer-9ec38fd5ea.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-a0e2a300fd.html b/ProjectIntakeTower/explainers/web/visual-explainer-a0e2a300fd.html new file mode 100644 index 0000000000000000000000000000000000000000..744bd18dec76f539c875ab6dc517595d7c453aba --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-a0e2a300fd.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/ph/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-a0e2a300fd.md · Video: visual-explainer-a0e2a300fd.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-d951b8da02.html b/ProjectIntakeTower/explainers/web/visual-explainer-d951b8da02.html new file mode 100644 index 0000000000000000000000000000000000000000..d761e9d7b1da4e5c507f6ecd7772b9e11fdb46b8 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-d951b8da02.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/ra/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-d951b8da02.md · Video: visual-explainer-d951b8da02.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-ea7953ee94.html b/ProjectIntakeTower/explainers/web/visual-explainer-ea7953ee94.html new file mode 100644 index 0000000000000000000000000000000000000000..61d749647af8c170cf958d8dafae4f8df0c3634a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-ea7953ee94.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/cnw/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-ea7953ee94.md · Video: visual-explainer-ea7953ee94.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/visual-explainer-efb23f0e9d.html b/ProjectIntakeTower/explainers/web/visual-explainer-efb23f0e9d.html new file mode 100644 index 0000000000000000000000000000000000000000..3f9d7981bd1a2928da2f22e809e2ce6d3268d8fa --- /dev/null +++ b/ProjectIntakeTower/explainers/web/visual-explainer-efb23f0e9d.html @@ -0,0 +1,6 @@ +visual-explainer — Visual Explainer

ProjectIntakeTower Visual Explainer

visual-explainer

/home/smlflg/.hermes/profiles/mlg/skills/visual-explainer

Tech: node · Score: 0 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Projektartefakt mit Schwerpunkt node, entdeckt über Repo-/Plan-/TODO-Signale.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System

+

Evidence

Score-Reasons

  • Keine Score-Reasons vorhanden

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: visual-explainer-efb23f0e9d.md · Video: visual-explainer-efb23f0e9d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/vizier-682eb96505.html b/ProjectIntakeTower/explainers/web/vizier-682eb96505.html new file mode 100644 index 0000000000000000000000000000000000000000..6a91a60a6557d23f291e5a02815e713e886cb2de --- /dev/null +++ b/ProjectIntakeTower/explainers/web/vizier-682eb96505.html @@ -0,0 +1,6 @@ +vizier — Visual Explainer

ProjectIntakeTower Visual Explainer

vizier

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier

Tech: docs/notes · Score: 22 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 8 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/astropy/io/ascii/tests/data/vizier/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: vizier-682eb96505.md · Video: vizier-682eb96505.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/vizier-cad7290909.html b/ProjectIntakeTower/explainers/web/vizier-cad7290909.html new file mode 100644 index 0000000000000000000000000000000000000000..3f26a380349aa21ed66c1f5d0fbe24e39eacf07b --- /dev/null +++ b/ProjectIntakeTower/explainers/web/vizier-cad7290909.html @@ -0,0 +1,6 @@ +vizier — Visual Explainer

ProjectIntakeTower Visual Explainer

vizier

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier

Tech: docs/notes · Score: 22 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 8 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/astropy/io/ascii/tests/data/vizier/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: vizier-cad7290909.md · Video: vizier-cad7290909.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/vizier-f83ad82235.html b/ProjectIntakeTower/explainers/web/vizier-f83ad82235.html new file mode 100644 index 0000000000000000000000000000000000000000..58f7b86010d5653f9d74afd791d8752fea9dcc95 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/vizier-f83ad82235.html @@ -0,0 +1,6 @@ +vizier — Visual Explainer

ProjectIntakeTower Visual Explainer

vizier

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier

Tech: docs/notes · Score: 22 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010) ================================================================================ Chemical abundance analysis of the open clusters Cr 110, N

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 8 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 8 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:1 — J/A+A/511/A56 Abundances of five open clusters (Pancino+, 2010)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:3 — Chemical abundance analysis of the open clusters Cr 110, NGC 2420, NGC 7789,
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:9 — ADC_Keywords: Clusters, open ; Stars, giant ; Equivalent widths ; Spectroscopy
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:11 — open clusters and associations: general
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:14 — The present number of Galactic open clusters that have high resolution
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/astropy/io/ascii/tests/data/vizier/ReadMe:18 — open clusters with high quality measurements, we obtained high
+

Storyboard: vizier-f83ad82235.md · Video: vizier-f83ad82235.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/voicemode-b0eec5ba24.html b/ProjectIntakeTower/explainers/web/voicemode-b0eec5ba24.html new file mode 100644 index 0000000000000000000000000000000000000000..9b4e52a30a59b02f736596b768233f114e972430 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/voicemode-b0eec5ba24.html @@ -0,0 +1,6 @@ +Voicemode — Visual Explainer

ProjectIntakeTower Visual Explainer

Voicemode

/home/smlflg/Projekte/Voicemode

Tech: docs/notes · Score: 16 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Voicemode — Samuel's Voice Setup Voice interaction for Claude Code on Pop!_OS/Wayland.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Voicemode/FOR_SMLFLG.md:101 — ## Next Steps (priorisiert)
+

Storyboard: voicemode-b0eec5ba24.md · Video: voicemode-b0eec5ba24.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/voicemode-edge-tts-2bafab700d.html b/ProjectIntakeTower/explainers/web/voicemode-edge-tts-2bafab700d.html new file mode 100644 index 0000000000000000000000000000000000000000..1209dab42d831805017c7bb9fe9a3415c8128ca0 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/voicemode-edge-tts-2bafab700d.html @@ -0,0 +1,6 @@ +voicemode-edge-tts — Visual Explainer

ProjectIntakeTower Visual Explainer

voicemode-edge-tts

/home/smlflg/Projekte/MyAIGame/voicemode-edge-tts

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

VoiceMode Edge TTS — Latency Optimizer Drop TTS latency from **~8s (Kokoro) to ~1.5s (Edge TTS)** by wrapping Microsoft Edge TTS as an OpenAI-compatible API server.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: voicemode-edge-tts-2bafab700d.md · Video: voicemode-edge-tts-2bafab700d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/vscode-f94c4b50f6.html b/ProjectIntakeTower/explainers/web/vscode-f94c4b50f6.html new file mode 100644 index 0000000000000000000000000000000000000000..fb37d46d694cb86b417438ae28db6f5a59d0ad00 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/vscode-f94c4b50f6.html @@ -0,0 +1,6 @@ +vscode — Visual Explainer

ProjectIntakeTower Visual Explainer

vscode

/home/smlflg/Projekte/Harness_swap/apps/vscode

Tech: node, typescript · Score: 4 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Ein Harness/Evaluation-System, um Agentenläufe messbar, vergleichbar und verifizierbar zu machen.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise, unklare/fehlende README-Evidenz

Was ist heute wertvoll?

Heute wertvoll als Ideenspeicher oder Archiv-Kandidat nach Review.

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Harness_swap/apps/vscode/package.json:20 — "title": "Harness Swap: Open Migration Wizard",
  • /home/smlflg/Projekte/Harness_swap/apps/vscode/src/wizardPanel.ts:358 — statusEl.textContent = "No workspace folders available. Open a folder and try again.";
+

Storyboard: vscode-f94c4b50f6.md · Video: vscode-f94c4b50f6.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/wcslib-3ae7dfb445.html b/ProjectIntakeTower/explainers/web/wcslib-3ae7dfb445.html new file mode 100644 index 0000000000000000000000000000000000000000..4807bacbad3e82d9a9fb9df6e37e38dd751cdba4 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/wcslib-3ae7dfb445.html @@ -0,0 +1,6 @@ +wcslib — Visual Explainer

ProjectIntakeTower Visual Explainer

wcslib

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

------------------------------------------------------------------------------ WCSLIB 7.7 and PGSBOX 7.7 ------------------------------------------------------------------------------ WCSLIB 7.7 - an implementation of th

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:9 — - In wcsutil_fptr2str(), fixed a bug reported by Ralf Palsa (with fix)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:56 — - Bug fix in tabs2x() triggered for 1-dimensional coordinate lookup
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:176 — - In wcshdo(), fixed a bug introduced in release 5.9 that potentially
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:184 — Also in wcshdo(), fixed a bug introduced in release 7.1 that caused
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:250 — - Bug fix in wcsfix() - it was writing error messages that referred
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_d16bfe05a744909de4b27f5875fe0d4ed41ce607/cextern/wcslib/CHANGES:291 — - In wcssub(), fixed a bug relating to handling coordinate lookup
+

Storyboard: wcslib-3ae7dfb445.md · Video: wcslib-3ae7dfb445.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/wcslib-5bb865636f.html b/ProjectIntakeTower/explainers/web/wcslib-5bb865636f.html new file mode 100644 index 0000000000000000000000000000000000000000..fd9076c5c0dc808a38b27005667890e84cfa326d --- /dev/null +++ b/ProjectIntakeTower/explainers/web/wcslib-5bb865636f.html @@ -0,0 +1,6 @@ +wcslib — Visual Explainer

ProjectIntakeTower Visual Explainer

wcslib

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

------------------------------------------------------------------------------ WCSLIB 7.12 and PGSBOX 7.12 ------------------------------------------------------------------------------ WCSLIB 7.12 - an implementation of

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:60 — - In wcsset(), bug fix for identifying time coordinate axes.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:69 — - In wcssub(), bug fix for tabular coordinates that change axis
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:89 — - Bug fix in the utils makefile for creating $(MANDIR)/man1.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:92 — - Bug fix in the Fortran makefile for compiling and using 'tofits'.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:108 — - In wcsutil_fptr2str(), fixed a bug reported by Ralf Palsa (with fix)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_7269fa3e33e8d02485a647da91a5a2a60a06af61/cextern/wcslib/CHANGES:155 — - Bug fix in tabs2x() triggered for 1-dimensional coordinate lookup
+

Storyboard: wcslib-5bb865636f.md · Video: wcslib-5bb865636f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/wcslib-78aabb88d0.html b/ProjectIntakeTower/explainers/web/wcslib-78aabb88d0.html new file mode 100644 index 0000000000000000000000000000000000000000..c23b19b0c32d919945c28f298b6af80c918deb45 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/wcslib-78aabb88d0.html @@ -0,0 +1,6 @@ +wcslib — Visual Explainer

ProjectIntakeTower Visual Explainer

wcslib

/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib

Tech: docs/notes · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

------------------------------------------------------------------------------ WCSLIB 7.12 and PGSBOX 7.12 ------------------------------------------------------------------------------ WCSLIB 7.12 - an implementation of

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:60 — - In wcsset(), bug fix for identifying time coordinate axes.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:69 — - In wcssub(), bug fix for tabular coordinates that change axis
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:89 — - Bug fix in the utils makefile for creating $(MANDIR)/man1.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:92 — - Bug fix in the Fortran makefile for compiling and using 'tofits'.
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:108 — - In wcsutil_fptr2str(), fixed a bug reported by Ralf Palsa (with fix)
  • /home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/astropy__astropy_a5917978be39d13cd90b517e1de4e7a539ffaa48/cextern/wcslib/CHANGES:155 — - Bug fix in tabs2x() triggered for 1-dimensional coordinate lookup
+

Storyboard: wcslib-78aabb88d0.md · Video: wcslib-78aabb88d0.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/web-0d9c4557ec.html b/ProjectIntakeTower/explainers/web/web-0d9c4557ec.html new file mode 100644 index 0000000000000000000000000000000000000000..f1c4679ad4d2547c41c42f28acc4635fe47bc6c6 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/web-0d9c4557ec.html @@ -0,0 +1,6 @@ +web — Visual Explainer

ProjectIntakeTower Visual Explainer

web

/home/smlflg/Projekte/Harness_swap/apps/web

Tech: node, typescript · Score: 14 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Harness Swap Web App Shell This folder contains a React + TypeScript + Vite frontend for: - drag-and-drop and file picker source ingestion - local migration orchestration behind a Web Worker boundary - structured diagnos

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Harness_swap/apps/web/README.md:9 — - ZIP package download for review/import
  • /home/smlflg/Projekte/Harness_swap/apps/web/src/App.tsx:174 — const enqueueFiles = useCallback((next: FileForIngestion[]) => {
  • /home/smlflg/Projekte/Harness_swap/apps/web/src/App.tsx:178 — for (const file of next) {
  • /home/smlflg/Projekte/Harness_swap/apps/web/src/App.tsx:188 — message: `Queued ${next.length} file(s) for migration.`
+

Storyboard: web-0d9c4557ec.md · Video: web-0d9c4557ec.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/websearchtool-078a3fa343.html b/ProjectIntakeTower/explainers/web/websearchtool-078a3fa343.html new file mode 100644 index 0000000000000000000000000000000000000000..8ff58d6fac96f2a42e3375b8a1c17282f58458b5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/websearchtool-078a3fa343.html @@ -0,0 +1,6 @@ +WebSearchTool — Visual Explainer

ProjectIntakeTower Visual Explainer

WebSearchTool

/home/smlflg/Projekte/derWolfimSchafspelz/openclaude/src/tools/WebSearchTool

Tech: docs/notes · Score: 14 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Web Search Providers OpenClaude supports multiple search backends through a provider adapter system.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 4 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 4 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/src/tools/WebSearchTool/providers/firecrawl.ts:14 — // TODO: @mendable/firecrawl-js SDK doesn't accept AbortSignal — can't cancel in-flight searches
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/src/tools/WebSearchTool/providers/duckduckgo.ts:22 — // TODO: duck-duck-scrape doesn't accept AbortSignal — can't cancel in-flight searches
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/src/tools/WebSearchTool/providers/index.ts:19 — * "auto" mode is the only mode that silently falls through to the next provider.
  • /home/smlflg/Projekte/derWolfimSchafspelz/openclaude/src/tools/WebSearchTool/providers/index.ts:179 — // Auto mode: log and try next
+

Storyboard: websearchtool-078a3fa343.md · Video: websearchtool-078a3fa343.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/websock-6cd8f8522e.html b/ProjectIntakeTower/explainers/web/websock-6cd8f8522e.html new file mode 100644 index 0000000000000000000000000000000000000000..af0ff9b98d17e27a6000e221c9239f23bb9e3273 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/websock-6cd8f8522e.html @@ -0,0 +1,6 @@ +websock — Visual Explainer

ProjectIntakeTower Visual Explainer

websock

/home/smlflg/Projekte/symphony/elixir/deps/websock

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

WebSock WebSock is a specification for apps to service WebSocket connections; you can think of it as 'Plug for WebSockets'.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: websock-6cd8f8522e.md · Video: websock-6cd8f8522e.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/websock_adapter-58f05d2b44.html b/ProjectIntakeTower/explainers/web/websock_adapter-58f05d2b44.html new file mode 100644 index 0000000000000000000000000000000000000000..fcdf6585734e1086728f57aba2d522999d988eb3 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/websock_adapter-58f05d2b44.html @@ -0,0 +1,6 @@ +websock_adapter — Visual Explainer

ProjectIntakeTower Visual Explainer

websock_adapter

/home/smlflg/Projekte/symphony/elixir/deps/websock_adapter

Tech: docs/notes · Score: 8 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

WebSockAdapter WebSockAdapter is a library of adapters from common Web Servers to the `WebSock` specification.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 1 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • 1 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/symphony/elixir/deps/websock_adapter/README.md:45 — sock.addEventListener("open", () => sock.send("ping"))
+

Storyboard: websock_adapter-58f05d2b44.md · Video: websock_adapter-58f05d2b44.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/websocket-35a776984f.html b/ProjectIntakeTower/explainers/web/websocket-35a776984f.html new file mode 100644 index 0000000000000000000000000000000000000000..118c1aec5f0e475f5ecc4986274386bb6b40cb49 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/websocket-35a776984f.html @@ -0,0 +1,6 @@ +websocket — Visual Explainer

ProjectIntakeTower Visual Explainer

websocket

/home/smlflg/Projekte/symphony/elixir/deps/bandit/lib/bandit/websocket

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

WebSocket Handler Included in this folder is a complete `ThousandIsland.Handler` based implementation of WebSockets as defined in [RFC 6455](https://datatracker.ietf.org/doc/rfc6455).

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: websocket-35a776984f.md · Video: websocket-35a776984f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/werbinich-4b2f31741d.html b/ProjectIntakeTower/explainers/web/werbinich-4b2f31741d.html new file mode 100644 index 0000000000000000000000000000000000000000..5a5bc03f4d5e7423c8bb5e16cfc3ea06aa822855 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/werbinich-4b2f31741d.html @@ -0,0 +1,6 @@ +WerBinIch — Visual Explainer

ProjectIntakeTower Visual Explainer

WerBinIch

/home/smlflg/Projekte/WerBinIch

Tech: python · Score: 59 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Wer bin ich Minimaler Python-CLI-Prototyp mit zwei KIs und einem Referee.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 20 TODO/FIXME-Hinweise, uncommitted changes

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 20 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/WerBinIch/research_packet.py:35 — with path.open("r", encoding="utf-8", newline="") as file:
  • /home/smlflg/Projekte/WerBinIch/research_packet.py:54 — with path.open("r", encoding="utf-8") as file:
  • /home/smlflg/Projekte/WerBinIch/compare_runs.py:21 — with summary_path.open("r", encoding="utf-8", newline="") as file:
  • /home/smlflg/Projekte/WerBinIch/whoami_game.py:111 — self.events_file = (log_dir / "events.jsonl").open("a", encoding="utf-8")
  • /home/smlflg/Projekte/WerBinIch/whoami_game.py:112 — self.transcript_file = (log_dir / "transcript.txt").open("a", encoding="utf-8")
  • /home/smlflg/Projekte/WerBinIch/single_player_eval.py:58 — self.events_file = (log_dir / "events.jsonl").open("a", encoding="utf-8")
+

Storyboard: werbinich-4b2f31741d.md · Video: werbinich-4b2f31741d.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/wg-agent-5f3e696824.html b/ProjectIntakeTower/explainers/web/wg-agent-5f3e696824.html new file mode 100644 index 0000000000000000000000000000000000000000..69d01c8cf50bfe3ed883dd18f3739eadcde5dc99 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/wg-agent-5f3e696824.html @@ -0,0 +1,6 @@ +WG-Agent — Visual Explainer

ProjectIntakeTower Visual Explainer

WG-Agent

/home/smlflg/Projekte/WG-Agent

Tech: python · Score: 31 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

WG-Agent WG-Agent is a local, review-first assistant for WG applications.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 40 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/WG-Agent/pyproject.toml:8 — description = "Review-first assistant for drafting personalized WG applications from pasted listings."
  • /home/smlflg/Projekte/WG-Agent/README.md:3 — WG-Agent is a local, review-first assistant for WG applications. Paste a listing from WG-Gesucht, Flats for Friends, Telegram, Facebook, or any other source; it extracts the useful
  • /home/smlflg/Projekte/WG-Agent/README.md:31 — wg-agent review
  • /home/smlflg/Projekte/WG-Agent/README.md:43 — wg-agent review
  • /home/smlflg/Projekte/WG-Agent/README.md:58 — Press Enter or Space for the next WG, or `q` to quit.
  • /home/smlflg/Projekte/WG-Agent/README.md:75 — To step through messages and open the matching listing tab automatically:
+

Storyboard: wg-agent-5f3e696824.md · Video: wg-agent-5f3e696824.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-008180d8aa.html b/ProjectIntakeTower/explainers/web/workflows-008180d8aa.html new file mode 100644 index 0000000000000000000000000000000000000000..0c326a01252c9bd32fe91dcd83966baac82b62be --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-008180d8aa.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/iap/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/iap/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/iap/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-008180d8aa.md · Video: workflows-008180d8aa.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-03ba811134.html b/ProjectIntakeTower/explainers/web/workflows-03ba811134.html new file mode 100644 index 0000000000000000000000000000000000000000..78bd9ab2c80d991b6ae75126308934905e6f3b72 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-03ba811134.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/cnw/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/cnw/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/cnw/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-03ba811134.md · Video: workflows-03ba811134.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-0e2ff873ed.html b/ProjectIntakeTower/explainers/web/workflows-0e2ff873ed.html new file mode 100644 index 0000000000000000000000000000000000000000..4e2121823b7d535c905606a7bd6e8ffb99953eca --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-0e2ff873ed.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/smk/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/smk/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/smk/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-0e2ff873ed.md · Video: workflows-0e2ff873ed.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-364680ae40.html b/ProjectIntakeTower/explainers/web/workflows-364680ae40.html new file mode 100644 index 0000000000000000000000000000000000000000..033a5d8da5b76ed9776a93ecbf7136acd4532ac7 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-364680ae40.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/decision-control/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/decision-control/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-364680ae40.md · Video: workflows-364680ae40.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-3968e67b0f.html b/ProjectIntakeTower/explainers/web/workflows-3968e67b0f.html new file mode 100644 index 0000000000000000000000000000000000000000..10c1ca508477714be351c0689435d47ddd014394 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-3968e67b0f.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/diagnosis/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/diagnosis/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-3968e67b0f.md · Video: workflows-3968e67b0f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-4415723ac3.html b/ProjectIntakeTower/explainers/web/workflows-4415723ac3.html new file mode 100644 index 0000000000000000000000000000000000000000..4af04d530d3a9dbf2055d520f42040f23826ccec --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-4415723ac3.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/ph/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ph/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/ph/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-4415723ac3.md · Video: workflows-4415723ac3.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-9a1871a1f5.html b/ProjectIntakeTower/explainers/web/workflows-9a1871a1f5.html new file mode 100644 index 0000000000000000000000000000000000000000..8339e3e885911135f527b4f7229bc20d4a9976ff --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-9a1871a1f5.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/openclaude-mcp/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-9a1871a1f5.md · Video: workflows-9a1871a1f5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-9b92dd170f.html b/ProjectIntakeTower/explainers/web/workflows-9b92dd170f.html new file mode 100644 index 0000000000000000000000000000000000000000..d7c138738df566981fe09102b2fd6cc68086aea5 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-9b92dd170f.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/ps/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ps/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/ps/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-9b92dd170f.md · Video: workflows-9b92dd170f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-a3d5dab414.html b/ProjectIntakeTower/explainers/web/workflows-a3d5dab414.html new file mode 100644 index 0000000000000000000000000000000000000000..c98bdbb46f016ec9da41260e6cb00938de718208 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-a3d5dab414.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/fixer/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/fixer/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/fixer/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-a3d5dab414.md · Video: workflows-a3d5dab414.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-a8fde53e91.html b/ProjectIntakeTower/explainers/web/workflows-a8fde53e91.html new file mode 100644 index 0000000000000000000000000000000000000000..ed927e7e232693e3011240b5f3daa3c90122ea61 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-a8fde53e91.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/ra/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/ra/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/ra/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-a8fde53e91.md · Video: workflows-a8fde53e91.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-a9cc6b75f5.html b/ProjectIntakeTower/explainers/web/workflows-a9cc6b75f5.html new file mode 100644 index 0000000000000000000000000000000000000000..47ca1de46620d72eadb6d7bd71f3b4856851bde9 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-a9cc6b75f5.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/dlm/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/dlm/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/dlm/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-a9cc6b75f5.md · Video: workflows-a9cc6b75f5.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-c515f6a67f.html b/ProjectIntakeTower/explainers/web/workflows-c515f6a67f.html new file mode 100644 index 0000000000000000000000000000000000000000..3b8434a12cd0cb129bd261a2a3fbef2ddda523d2 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-c515f6a67f.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/oktopus-minimal/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/oktopus-minimal/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/oktopus-minimal/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-c515f6a67f.md · Video: workflows-c515f6a67f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-ebaef1f405.html b/ProjectIntakeTower/explainers/web/workflows-ebaef1f405.html new file mode 100644 index 0000000000000000000000000000000000000000..87df987ebcd8dae5ffeefbb5a0c7cf0606f894fc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-ebaef1f405.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/voice-learning/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/voice-learning/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-ebaef1f405.md · Video: workflows-ebaef1f405.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workflows-f91af5ebbb.html b/ProjectIntakeTower/explainers/web/workflows-f91af5ebbb.html new file mode 100644 index 0000000000000000000000000000000000000000..81275c60948abedb84a757db5c386adb540c549a --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workflows-f91af5ebbb.html @@ -0,0 +1,6 @@ +workflows — Visual Explainer

ProjectIntakeTower Visual Explainer

workflows

/home/smlflg/.hermes/profiles/mlg/skills/creative/comfyui/workflows

Tech: docs/notes · Score: 10 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Example Workflows These are starter API-format workflows for the most common tasks.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 2 TODO/FIXME-Hinweise

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, dokumentierte Absicht

+

Evidence

Score-Reasons

  • 2 TODO/FIXME/WIP hints
  • README present

TODO/FIXME-Auszug

  • /home/smlflg/.hermes/profiles/mlg/skills/creative/comfyui/workflows/README.md:65 — with `class_type`), not editor format. To open them in ComfyUI's web UI for
  • /home/smlflg/.hermes/profiles/mlg/skills/creative/comfyui/workflows/README.md:66 — visual editing, use `Workflow → Load (API Format)` or `Workflow → Open` and
+

Storyboard: workflows-f91af5ebbb.md · Video: workflows-f91af5ebbb.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/workspace-mcp-ed66caa09f.html b/ProjectIntakeTower/explainers/web/workspace-mcp-ed66caa09f.html new file mode 100644 index 0000000000000000000000000000000000000000..e44d2fdc84ef964e2341ba14d49f872d45f69598 --- /dev/null +++ b/ProjectIntakeTower/explainers/web/workspace-mcp-ed66caa09f.html @@ -0,0 +1,6 @@ +workspace-mcp — Visual Explainer

ProjectIntakeTower Visual Explainer

workspace-mcp

/home/smlflg/Projekte/Connector/google-workspace/upstream/source/helm-chart/workspace-mcp

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Google Workspace MCP Server Helm Chart This Helm chart deploys the Google Workspace MCP Server on a Kubernetes cluster.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: workspace-mcp-ed66caa09f.md · Video: workspace-mcp-ed66caa09f.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/yamerl-51deb1b4cb.html b/ProjectIntakeTower/explainers/web/yamerl-51deb1b4cb.html new file mode 100644 index 0000000000000000000000000000000000000000..1daea85e7320559dd5b9964fb0ebe842f568fdbc --- /dev/null +++ b/ProjectIntakeTower/explainers/web/yamerl-51deb1b4cb.html @@ -0,0 +1,6 @@ +yamerl — Visual Explainer

ProjectIntakeTower Visual Explainer

yamerl

/home/smlflg/Projekte/symphony/elixir/deps/yamerl

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

yamerl: YAML 1.2 and JSON parser in Erlang YAML is a human-friendly data serialization format.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: yamerl-51deb1b4cb.md · Video: yamerl-51deb1b4cb.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/yaml_elixir-164965e2ed.html b/ProjectIntakeTower/explainers/web/yaml_elixir-164965e2ed.html new file mode 100644 index 0000000000000000000000000000000000000000..f875285272a74500a590de49ec857fce48cbe73c --- /dev/null +++ b/ProjectIntakeTower/explainers/web/yaml_elixir-164965e2ed.html @@ -0,0 +1,6 @@ +yaml_elixir — Visual Explainer

ProjectIntakeTower Visual Explainer

yaml_elixir

/home/smlflg/Projekte/symphony/elixir/deps/yaml_elixir

Tech: docs/notes · Score: 6 · Risk: low · Dirty: unknown

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

YAML Parser for Elixir This is a wrapper for [yamerl](https://github.com/yakaz/yamerl) - a native Erlang `YAML` parser which brings all of the functionalities to Elixir language.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht eindeutig unfertig; braucht fokussierte Verifikation statt Bauchgefühl.

Was ist heute wertvoll?

Heute wertvoll als dokumentierte Absicht

+

Evidence

Score-Reasons

  • README present

TODO/FIXME-Auszug

  • Keine TODO-Snippets im Intake-Kontext.
+

Storyboard: yaml_elixir-164965e2ed.md · Video: yaml_elixir-164965e2ed.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/explainers/web/zentrale-193cdb6361.html b/ProjectIntakeTower/explainers/web/zentrale-193cdb6361.html new file mode 100644 index 0000000000000000000000000000000000000000..cb78eef4a34e1817295a27a6658d9eeb4511b68f --- /dev/null +++ b/ProjectIntakeTower/explainers/web/zentrale-193cdb6361.html @@ -0,0 +1,6 @@ +Zentrale — Visual Explainer

ProjectIntakeTower Visual Explainer

Zentrale

/home/smlflg/Projekte/Zentrale

Tech: agent, python · Score: 70 · Risk: medium · Dirty: True

+

Systembild

Originale IdeeProblem sichtbar machenBuild-SpurenGit · README · Pläne · TODOsHeutiger WertWeiterbauen oder archivierenOffener Loop: Abschlussartefakt → Verifier → Issue/Handoff +

Was war die Idee?

Zentrale Lokale adaptive Agent-Zentrale fuer Projektstart, Routing, Context Packs und Harness-Delegation.

Warum angefangen?

Gestartet, um wiederholte Arbeit zu operationalisieren: Kontext sammeln, Entscheidungen sichtbar machen und Agentenarbeit prüfbar machen.

Warum nicht fertig?

Nicht fertig, weil Abschluss-Signale fehlen: 40 TODO/FIXME-Hinweise, uncommitted changes, 1 alte Pläne/Handoffs

Was ist heute wertvoll?

Heute wertvoll als Agent-Control-System, hoher Intake-Score, dokumentierte Absicht, Git-Historie

+

Evidence

Score-Reasons

  • git repo
  • tracked dirty work
  • 40 TODO/FIXME/WIP hints
  • README present
  • agentized
  • plans/backlogs found

TODO/FIXME-Auszug

  • /home/smlflg/Projekte/Zentrale/solution6:26 — Das Gute: Jeder Baustein existiert teilweise in der Open-Source-Welt. Das Schwierige: Die Kombination aller drei mit genau deinen 5 Harnesses gibt es so wahrscheinlich nicht fertig
  • /home/smlflg/Projekte/Zentrale/DEVELOP.md:250 — - No automatic MD self-modification without human review (by design)
  • /home/smlflg/Projekte/Zentrale/README.md:79 — | `5` | Phases | Phase-Pills mit `←/→`, Next Phase, Save |
  • /home/smlflg/Projekte/Zentrale/solution4:79 — BridgeMind ist kein klassisches Open-Source-GitHub-Basisprojekt, aber als Produkt sehr nah an deinem Zielbild. Es positioniert sich mit **BridgeSpace** als agentischer Entwicklungs
  • /home/smlflg/Projekte/Zentrale/solution4:85 — Weil du explizit nach **GitHub-Projekten / modifizierbaren Basen** suchst. BridgeMind ist eher Inspirationsquelle oder möglicher Fremdbezug als dein Hack-Startpunkt. ([BridgeMind][
  • /home/smlflg/Projekte/Zentrale/solution4:153 — **“v1 Kommandozentrale = orchestrierter Projektstarter mit statischer Profilwahl + Worktree-Isolation + Review”**
+

Storyboard: zentrale-193cdb6361.md · Video: zentrale-193cdb6361.mp4

\ No newline at end of file diff --git a/ProjectIntakeTower/github/gh_create_issues.sh b/ProjectIntakeTower/github/gh_create_issues.sh new file mode 100644 index 0000000000000000000000000000000000000000..c6c7e9884ee40a02a39144580df865b0e6989fed --- /dev/null +++ b/ProjectIntakeTower/github/gh_create_issues.sh @@ -0,0 +1,38 @@ +#!/usr/bin/env bash +set -euo pipefail + +# Human-gated script. Do not run blindly. +# Usage after reviewing drafts: +# DRY_RUN=1 ./github/gh_create_issues.sh +# DRY_RUN=0 ./github/gh_create_issues.sh + +ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)" +DRAFT_DIR="$ROOT/github/issue_drafts" +DRY_RUN="${DRY_RUN:-1}" + +if ! command -v gh >/dev/null 2>&1; then + echo "gh CLI not found" >&2 + exit 2 +fi + +gh auth status >/dev/null + +find "$DRAFT_DIR" -type f -name '*.md' | sort | while read -r draft; do + title="$(grep -m1 '^Title:' "$draft" | sed 's/^Title:[[:space:]]*//')" + repo="$(grep -m1 '^Repo:' "$draft" | sed 's/^Repo:[[:space:]]*//')" + labels="$(grep -m1 '^Labels:' "$draft" | sed 's/^Labels:[[:space:]]*//')" + + if [[ -z "$title" || -z "$repo" ]]; then + echo "SKIP missing Title/Repo: $draft" >&2 + continue + fi + + echo "ISSUE draft=$draft repo=$repo title=$title labels=$labels" + if [[ "$DRY_RUN" == "0" ]]; then + if [[ -n "$labels" ]]; then + gh issue create --repo "$repo" --title "$title" --body-file "$draft" --label "$labels" + else + gh issue create --repo "$repo" --title "$title" --body-file "$draft" + fi + fi +done diff --git a/ProjectIntakeTower/github/issue_drafts/.claude/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/.claude/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..0040ad180242e996f10c1cefc6c0628425e2169f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/.claude/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for .claude +Repo: https://github.com/Erdnussspalter/claude-config.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.claude` +- Status: active +- TODO count: 4498 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/.codex/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/.codex/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..6b7c2033a8f6aebe045b4fec228849360f5673a7 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/.codex/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for .codex +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.codex` +- Status: active +- TODO count: 12867 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/.hermes/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/.hermes/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..f403ff3068c15bf41ec34e3f267000c44ed340e0 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/.hermes/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for .hermes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.hermes` +- Status: quick_win +- TODO count: 2723 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/ACT-agentcommandotower/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/ACT-agentcommandotower/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..706d15f31f92ba8e96fde9ba5baaf198383139c5 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ACT-agentcommandotower/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for ACT-agentcommandotower +Repo: https://github.com/smlfg/ACT-agentcommandotower.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/ACT-agentcommandotower` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/AIOS-Cockpit/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/AIOS-Cockpit/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..a7e9b145763c6d24b5365cda8e7a7ae5d04b0a05 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/AIOS-Cockpit/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for AIOS-Cockpit +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/AIOS-Cockpit` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/AgentArena/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/AgentArena/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..04e77600b12ae386520a5f4ee501cf0eec2edf2c --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/AgentArena/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for AgentArena +Repo: https://github.com/smlfg/AgentArena.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/AgentArena` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/AgentIDE/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/AgentIDE/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..7712628a7edd3e87ff2d51fea1bb5631eedd9628 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/AgentIDE/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for AgentIDE +Repo: https://github.com/Erdnussspalter/AgentIDE.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/AgentIDE` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/AgentTestUniSupport/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/AgentTestUniSupport/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..69f42ab1e11079c483e82ee68f7011c6a79345dc --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/AgentTestUniSupport/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for AgentTestUniSupport +Repo: https://github.com/smlfg/uni-agent.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Jobs_Selbständigkeit_Geldverdienen/AgentTestUniSupport` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/BahnAgent/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/BahnAgent/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..f0694e40304820aa73a9a51477f57c88bcc1ba03 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/BahnAgent/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for BahnAgent +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/BahnAgent` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/BuildingTheWorld/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/BuildingTheWorld/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..d3907c8984d04c6a23a04a8c4f2574d39152d943 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/BuildingTheWorld/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for BuildingTheWorld +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/BuildingTheWorld` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/ClaudeCodePanel/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/ClaudeCodePanel/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..484365590e86ef08a5e1d2dc52626974f994158d --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ClaudeCodePanel/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for ClaudeCodePanel +Repo: https://github.com/smlfg/ClaudeCodePanel.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/ClaudeCodePanel` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/CloudCodeUsageAnalysis/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/CloudCodeUsageAnalysis/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..aeb0d442fba226a007d44f3b60cb80ca1305c597 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/CloudCodeUsageAnalysis/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for CloudCodeUsageAnalysis +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/CloudCodeUsageAnalysis` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/CodexDashBoard/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/CodexDashBoard/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..11f3febcd78b1c1e0ec13d9993bcff4d6e9b4e55 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/CodexDashBoard/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for CodexDashBoard +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/CodexDashBoard` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/FrontierLLMHarnessValidation/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/FrontierLLMHarnessValidation/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..1f52377f7e41dce89b0323af1edbf8a26094d1e5 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/FrontierLLMHarnessValidation/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for FrontierLLMHarnessValidation +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/FrontierLLMHarnessValidation` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/HD-St.Anton/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/HD-St.Anton/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..65cada6a22a273fd54dc760ecad965a3da1c9456 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/HD-St.Anton/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for HD-St.Anton +Repo: https://github.com/smlfg/st-anton-trip.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/BahnAgent/HD-St.Anton` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/HarnessEcosystem/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/HarnessEcosystem/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..93418d6fdf4a8dccd994fe75ab470cfebde954fb --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/HarnessEcosystem/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for HarnessEcosystem +Repo: https://github.com/smlfg/HarnessEcosystem.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/HarnessEcosystem` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/HeumandenParty/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/HeumandenParty/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..494df3b1a7d6dcbceb5e830045434330368f7db2 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/HeumandenParty/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for HeumandenParty +Repo: https://github.com/smlfg/heumaden-lenzzauber.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/HeumandenParty` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdienen/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdienen/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..1c068321d235c4d850ad439acd7ebebcc3628109 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdienen/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Jobs_Selbständigkeit_Geldverdienen +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Jobs_Selbständigkeit_Geldverdienen` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdieren/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdieren/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..7c0ca57c7c4837201d79f68ea7266c2127d05242 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Jobs_Selbst_ndigkeit_Geldverdieren/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Jobs_Selbständigkeit_Geldverdieren +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Jobs_Selbständigkeit_Geldverdieren` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/LuisHandoff/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/LuisHandoff/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..4b245834a1ef25cf0155bf83532ab112626fccfd --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/LuisHandoff/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for LuisHandoff +Repo: https://github.com/smlfg/LuisHandoff.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/LuisHandoff` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/MetaMetaMeta/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/MetaMetaMeta/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..7d89a9195c84fc36a05c563453e75c73bab94343 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/MetaMetaMeta/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for MetaMetaMeta +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/MetaMetaMeta` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/NasaCode/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/NasaCode/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..1028a180ac51ee835803f48a6b9363b04226dd8e --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/NasaCode/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for NasaCode +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/NasaCode` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/PortfolioTimeline/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/PortfolioTimeline/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..a9d78fb46b6f4b5cc1e4bd3135ed5aa43417a0a0 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/PortfolioTimeline/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for PortfolioTimeline +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/PortfolioTimeline` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/ProjectDashboard/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/ProjectDashboard/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..50af92bc3b4c2e85bb05f97ae33c3829cd606d60 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ProjectDashboard/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for ProjectDashboard +Repo: https://github.com/smlfg/ProjectDashboard.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/ProjectDashboard` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Projekte/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Projekte/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..1288c3541ad682e1ff4144a483f5ee2929cbf6e6 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Projekte/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Projekte +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte` +- Status: needs_human +- TODO count: 4910 +- Verification: failed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/PromptGarageUI/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/PromptGarageUI/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..83d712f22da75ef787f3e4c86ecd252eceda5cc2 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/PromptGarageUI/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for PromptGarageUI +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/PromptGarageUI` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/PseudoLogikPyhthonCPP/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/PseudoLogikPyhthonCPP/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..f672622d5cc22d39d436732953bfa678c8259dad --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/PseudoLogikPyhthonCPP/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for PseudoLogikPyhthonCPP +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/PseudoLogikPyhthonCPP` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/SessionDesktopMonitor/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/SessionDesktopMonitor/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..d7cf234c4ba2c64db49d2928732b6f7bee219dd9 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/SessionDesktopMonitor/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for SessionDesktopMonitor +Repo: https://github.com/smlfg/SessionDesktopMonitor.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/SessionDesktopMonitor` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/ShortcutCounter/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/ShortcutCounter/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..a558844bacfb58915064b9d0cd84bdd95bdb6a47 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ShortcutCounter/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for ShortcutCounter +Repo: https://github.com/smlfg/ShortcutCounter.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/ShortcutCounter` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-Evolution/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-Evolution/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..44dfbb37651aa6d8690b6f86af010d0915799758 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-Evolution/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-Evolution +Repo: https://github.com/smlfg/Sidecar-Evolution.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-Evolution` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-V5/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-V5/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..e9ddfc878ab2deba05cb32d8468b923703d73a9a --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-V5/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-V5 +Repo: https://github.com/smlfg/personal-sidecar.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-V7-Lite/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-V7-Lite/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..2ac388579216d9471ee185fa597522ae28f5a7d4 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-V7-Lite/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-V7-Lite +Repo: https://github.com/smlfg/Sidecar-V7-Lite.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-V7/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-V7/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..75a3dc80cb393519cc46e2dda4e4328b2fa6ed54 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-V7/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-V7 +Repo: https://github.com/smlfg/Sidecar-V7.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-V8/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-V8/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..968dd3f997e3577de627b9d8264980cf2ef644db --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-V8/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-V8 +Repo: https://github.com/smlfg/Sidecar-V8.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-ng-dashboard/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-ng-dashboard/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..65d586ba661bcd77d889b4d1dfda3d0543d21953 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-ng-dashboard/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-ng-dashboard +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar-ng/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar-ng/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..91e8666129b020b29f5b7ebe167908b604c10949 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar-ng/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar-ng +Repo: https://github.com/smlfg/Sidecar-ng.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Sidecar/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Sidecar/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..2b91fdaf25691ae1202110ce33288642ed2ca62b --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Sidecar/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Sidecar +Repo: https://github.com/smlfg/Sidecar.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/SidecarDashboard/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/SidecarDashboard/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..bcc9262210a6500ce08b77f4395f959665ae422f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/SidecarDashboard/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for SidecarDashboard +Repo: https://github.com/smlfg/SidecarDashboard.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/SidecarDashboard` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/StudyAgent/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/StudyAgent/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..e70c929e6b4b3668dc20516b9e3e860d2bad3438 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/StudyAgent/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for StudyAgent +Repo: https://github.com/smlfg/StudyAgent.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/StudyAgent` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/UEBER_AGENT/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/UEBER_AGENT/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..191a1935c9084c4bb1c17c93bb215059d5f259e9 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/UEBER_AGENT/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for UEBER_AGENT +Repo: https://github.com/smlfg/UEBER_AGENT.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/UEBER_AGENT` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/WerBinIch/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/WerBinIch/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..24d51ef0f0c9aec280cd4ab719065e6bcda4b157 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/WerBinIch/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for WerBinIch +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/WerBinIch` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/Zentrale/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/Zentrale/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..d0b4dc9393faad3230f333821b66f65064654900 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/Zentrale/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for Zentrale +Repo: https://github.com/smlfg/Zentrale.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Zentrale` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/act-agentcommandotower-0112bb030d.md b/ProjectIntakeTower/github/issue_drafts/act-agentcommandotower-0112bb030d.md new file mode 100644 index 0000000000000000000000000000000000000000..1850d431b261ff4b09ff679d004235293faa7b86 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/act-agentcommandotower-0112bb030d.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] ACT-agentcommandotower: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/ACT-agentcommandotower` +- Status: `active` +- Score: `69` +- Risk: `medium` +- Technologies: agent +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/act-agentcommandotower-0112bb030d.md` +- Evidence file: `inventory/evidence/act-agentcommandotower-0112bb030d.json` +- TODO/FIXME/WIP hints: 19 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-act-agentcommandotower-0112bb030d-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/agentarena-a78ddede96.md b/ProjectIntakeTower/github/issue_drafts/agentarena-a78ddede96.md new file mode 100644 index 0000000000000000000000000000000000000000..997379a57dee6b8735280ae9d0f09991c0cce5cf --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/agentarena-a78ddede96.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] AgentArena: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/AgentArena` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 10 + +## Evidence + +- Project card: `inventory/project_cards/agentarena-a78ddede96.md` +- Evidence file: `inventory/evidence/agentarena-a78ddede96.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-agentarena-a78ddede96-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/agentide-a18ec596a3.md b/ProjectIntakeTower/github/issue_drafts/agentide-a18ec596a3.md new file mode 100644 index 0000000000000000000000000000000000000000..17c5020b8cad4d9d11b014ba39a2ad394abb0f32 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/agentide-a18ec596a3.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] AgentIDE: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/AgentIDE` +- Status: `needs_human` +- Score: `54` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 3 + +## Evidence + +- Project card: `inventory/project_cards/agentide-a18ec596a3.md` +- Evidence file: `inventory/evidence/agentide-a18ec596a3.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 1 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-agentide-a18ec596a3-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/agenttestunisupport-a891990bc1.md b/ProjectIntakeTower/github/issue_drafts/agenttestunisupport-a891990bc1.md new file mode 100644 index 0000000000000000000000000000000000000000..5a2bffe55619141a4a7ee3703a13c3adeb2556c2 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/agenttestunisupport-a891990bc1.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] AgentTestUniSupport: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Jobs_Selbständigkeit_Geldverdienen/AgentTestUniSupport` +- Status: `active` +- Score: `63` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 12 + +## Evidence + +- Project card: `inventory/project_cards/agenttestunisupport-a891990bc1.md` +- Evidence file: `inventory/evidence/agenttestunisupport-a891990bc1.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 4 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-agenttestunisupport-a891990bc1-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/aidvance-proposal/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/aidvance-proposal/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..ee9d0267c5140ed8322a11ce9d0e15d0d5292633 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/aidvance-proposal/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for aidvance-proposal +Repo: https://github.com/smlfg/aidvance-proposal.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Jobs_Selbständigkeit_Geldverdienen/aidvance-proposal` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/aios-cockpit-0ba0ee2b88.md b/ProjectIntakeTower/github/issue_drafts/aios-cockpit-0ba0ee2b88.md new file mode 100644 index 0000000000000000000000000000000000000000..7e8df8aa54d15c9bf6089f34350e77d2269bafb9 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/aios-cockpit-0ba0ee2b88.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] AIOS-Cockpit: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/AIOS-Cockpit` +- Status: `active` +- Score: `54` +- Risk: `low` +- Technologies: agent, python +- Git dirty tracked files: 0 + +## Evidence + +- Project card: `inventory/project_cards/aios-cockpit-0ba0ee2b88.md` +- Evidence file: `inventory/evidence/aios-cockpit-0ba0ee2b88.json` +- TODO/FIXME/WIP hints: 22 +- Plan hits: 5 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-aios-cockpit-0ba0ee2b88-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/alleProjekte/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/alleProjekte/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..a2fb02bb5b69ac7177cbc22d6be8c46e4e5b80cc --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/alleProjekte/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for alleProjekte +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/alleProjekte` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/claude-insights-timeline/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/claude-insights-timeline/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..d5ab2a6c8ff6d45ff99423f33deb093069c94e55 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/claude-insights-timeline/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for claude-insights-timeline +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/claude-insights-timeline` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/claudecodepanel-7a5151f720.md b/ProjectIntakeTower/github/issue_drafts/claudecodepanel-7a5151f720.md new file mode 100644 index 0000000000000000000000000000000000000000..2bdafc753207f9a0dcc850aec8011a39f02cc592 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/claudecodepanel-7a5151f720.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] ClaudeCodePanel: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/ClaudeCodePanel` +- Status: `active` +- Score: `70` +- Risk: `medium` +- Technologies: agent, python +- Git dirty tracked files: 2 + +## Evidence + +- Project card: `inventory/project_cards/claudecodepanel-7a5151f720.md` +- Evidence file: `inventory/evidence/claudecodepanel-7a5151f720.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 1 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-claudecodepanel-7a5151f720-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/codex-sidecarV1/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/codex-sidecarV1/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..1a2f44be00c70e46f6358c92c0e3f141d63b5014 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/codex-sidecarV1/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for codex-sidecarV1 +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/codex-sidecarV1` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/codex-sidecarv1-60460fee07.md b/ProjectIntakeTower/github/issue_drafts/codex-sidecarv1-60460fee07.md new file mode 100644 index 0000000000000000000000000000000000000000..68e283c9bced4fc75f4dbb0328a35b8d2f1815cf --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/codex-sidecarv1-60460fee07.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] codex-sidecarV1: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/codex-sidecarV1` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/codex-sidecarv1-60460fee07.md` +- Evidence file: `inventory/evidence/codex-sidecarv1-60460fee07.json` +- TODO/FIXME/WIP hints: 20 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-codex-sidecarv1-60460fee07-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/codexdashboard-85a6fcfb79.md b/ProjectIntakeTower/github/issue_drafts/codexdashboard-85a6fcfb79.md new file mode 100644 index 0000000000000000000000000000000000000000..09b0a4dd5eab5fc91da3e3eda396366a2d5696aa --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/codexdashboard-85a6fcfb79.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] CodexDashBoard: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/CodexDashBoard` +- Status: `active` +- Score: `51` +- Risk: `low` +- Technologies: hermes-async, python +- Git dirty tracked files: 0 + +## Evidence + +- Project card: `inventory/project_cards/codexdashboard-85a6fcfb79.md` +- Evidence file: `inventory/evidence/codexdashboard-85a6fcfb79.json` +- TODO/FIXME/WIP hints: 27 +- Plan hits: 2 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-codexdashboard-85a6fcfb79-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/commands/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/commands/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..8ccdb74382dbf02ad03e54a7d17e4cf963a2408b --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/commands/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for commands +Repo: https://github.com/Erdnussspalter/claude-config-commands.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.claude/commands` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/commit-repo/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/commit-repo/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..4cbec8ffc2fb230941a44474483f7d821af76721 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/commit-repo/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for commit-repo +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/codex-skill-validation-fixtures/commit-repo` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa.md b/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa.md new file mode 100644 index 0000000000000000000000000000000000000000..dcce62f4035dcc23b7ae0eb2c6d7a76837b7530c --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: node, python +- Git dirty tracked files: 4 + +## Evidence + +- Project card: `inventory/project_cards/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa.md` +- Evidence file: `inventory/evidence/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a-10ca4c1baa-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..f26362d1745eb7d80023bc2f2545fe39b413242b --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a +Repo: https://github.com/django/django.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8.md b/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8.md new file mode 100644 index 0000000000000000000000000000000000000000..b808187391d1212ce3baeecb6f8012a05b0921a8 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] django__django_bceadd2788dc2dad53eba0caae172bd8522fd483: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: node, python +- Git dirty tracked files: 4 + +## Evidence + +- Project card: `inventory/project_cards/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8.md` +- Evidence file: `inventory/evidence/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-django__django_bceadd2788dc2dad53eba0caae172bd8522fd483-0a6852d7c8-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..9c3c2d2743ae6584b750ad6eb08ad8b2c6d176fa --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for django__django_bceadd2788dc2dad53eba0caae172bd8522fd483 +Repo: https://github.com/django/django.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/01_.hermes.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/01_.hermes.md new file mode 100644 index 0000000000000000000000000000000000000000..1abd5a3fb9c1c98d64bcc6f5f6d6101096701361 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/01_.hermes.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/.hermes` + +## Why +44 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/02_.hermes_profiles_ra.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/02_.hermes_profiles_ra.md new file mode 100644 index 0000000000000000000000000000000000000000..caeef6b9390fc5c16c63e0730260ff90088fcfcd --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/02_.hermes_profiles_ra.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/.hermes/profiles/ra` + +## Why +34 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/03_Projekte_Zentrale.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/03_Projekte_Zentrale.md new file mode 100644 index 0000000000000000000000000000000000000000..f37e324343c8512b3fd930ac18cca419dac81109 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/03_Projekte_Zentrale.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/Zentrale` + +## Why +20 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/04_Projekte_Sidecar-Workspace_Sidecar-ng-dashboard.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/04_Projekte_Sidecar-Workspace_Sidecar-ng-dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..deaafdf218bf8ee3f589796d3d5ad78fb7b857c1 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/04_Projekte_Sidecar-Workspace_Sidecar-ng-dashboard.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng-dashboard` + +## Why +15 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/05_Projekte_Sidecar-Workspace_Sidecar.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/05_Projekte_Sidecar-Workspace_Sidecar.md new file mode 100644 index 0000000000000000000000000000000000000000..b52352c81f0f972f76f67d8d1b340959e7844d7e --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/05_Projekte_Sidecar-Workspace_Sidecar.md @@ -0,0 +1,17 @@ +Title: Decide merge/archive direction +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/Sidecar-Workspace/Sidecar` + +## Why +duplicate cluster: sidecar (8 repos) + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +human decision + merge plan diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/06_Projekte_codex-skill-validation-fixtures_commit-repo.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/06_Projekte_codex-skill-validation-fixtures_commit-repo.md new file mode 100644 index 0000000000000000000000000000000000000000..aa6e3d367a24037b47d160c8e1f1e7f23068db7f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/06_Projekte_codex-skill-validation-fixtures_commit-repo.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/codex-skill-validation-fixtures/commit-repo` + +## Why +3 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/07_Projekte_AgentArena.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/07_Projekte_AgentArena.md new file mode 100644 index 0000000000000000000000000000000000000000..3c8a038eb8c15fdb902387435b62dfe6510dd81f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/07_Projekte_AgentArena.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/AgentArena` + +## Why +12 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/08_Projekte_AIOS-Cockpit.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/08_Projekte_AIOS-Cockpit.md new file mode 100644 index 0000000000000000000000000000000000000000..cac71553904ad2c0c7bbc4e04e7c1111cbfbb4fd --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/08_Projekte_AIOS-Cockpit.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/AIOS-Cockpit` + +## Why +12 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/09_Projekte_CodexDashBoard.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/09_Projekte_CodexDashBoard.md new file mode 100644 index 0000000000000000000000000000000000000000..8248cfdeab7fe22090523b4de7c3eddaf61c0a01 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/09_Projekte_CodexDashBoard.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/CodexDashBoard` + +## Why +12 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/focused_top10/10_Projekte_ACT-agentcommandotower.md b/ProjectIntakeTower/github/issue_drafts/focused_top10/10_Projekte_ACT-agentcommandotower.md new file mode 100644 index 0000000000000000000000000000000000000000..87896cff5105769580b78f43189115c5c0f0ee15 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/focused_top10/10_Projekte_ACT-agentcommandotower.md @@ -0,0 +1,17 @@ +Title: Stabilize uncommitted changes +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Path +`/home/smlflg/Projekte/ACT-agentcommandotower` + +## Why +7 uncommitted changes; preserve/triage before more agent work + +## Acceptance criteria +- Focused finding verified against repo state. +- Safe next action documented. +- No commit/push/merge without Samuel approval. + +## Verifier +git status + no commit without approval diff --git a/ProjectIntakeTower/github/issue_drafts/hd-st.anton-0d6574198f.md b/ProjectIntakeTower/github/issue_drafts/hd-st.anton-0d6574198f.md new file mode 100644 index 0000000000000000000000000000000000000000..6a32b9f2ecbd2d57a3ab8501979cc83792be410f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/hd-st.anton-0d6574198f.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] HD-St.Anton: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/BahnAgent/HD-St.Anton` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: docs/notes +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/hd-st.anton-0d6574198f.md` +- Evidence file: `inventory/evidence/hd-st.anton-0d6574198f.json` +- TODO/FIXME/WIP hints: 36 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-hd-st.anton-0d6574198f-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/hermes-agent/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/hermes-agent/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..36d0a9cb2029460e45ed3289dfa0a8fe73c023df --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/hermes-agent/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for hermes-agent +Repo: https://github.com/NousResearch/hermes-agent.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.hermes/hermes-agent` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/intake-archive-dead-prototype-xyz.md b/ProjectIntakeTower/github/issue_drafts/intake-archive-dead-prototype-xyz.md new file mode 100644 index 0000000000000000000000000000000000000000..6333689d624af17e0c66215727f881cd5e29612a --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/intake-archive-dead-prototype-xyz.md @@ -0,0 +1,25 @@ +# [ProjectIntakeTower] Find the intended dead prototype XYZ candidate from inventory evidence and produce an archive recommendation. Do not move/delete/archive anything. + +Labels: intake, agent-job, read-only, archive-candidate, needs-human, token-burn-safe + +## Intake command + +- Job: `intake-archive-dead-prototype-xyz` +- Project: `XYZ prototype candidate` +- Path/scope: `/home/smlflg/Projekte` +- Mode: `review_only` + +## Safety + +- Review-only by default. +- No source project modifications. +- No secrets, commits, pushes, deletes, or automatic issue creation. + +## Expected artifacts + +- `jobs/done/intake-archive-dead-prototype-xyz/result.json` +- `jobs/done/intake-archive-dead-prototype-xyz/archive_review.md` + +## Verifier + +`python3 verifier/verify_artifacts.py --job jobs/pending/intake-archive-dead-prototype-xyz.json --require-done` diff --git a/ProjectIntakeTower/github/issue_drafts/intake-audit-komandozentral.md b/ProjectIntakeTower/github/issue_drafts/intake-audit-komandozentral.md new file mode 100644 index 0000000000000000000000000000000000000000..56c522fea0464f8e07f55a8663e7b6fd6efd3c10 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/intake-audit-komandozentral.md @@ -0,0 +1,25 @@ +# [ProjectIntakeTower] Audit KomandoZentral read-only and produce an owner-facing audit: purpose, state, risks, verifier status, and one next action. + +Labels: intake, agent-job, read-only, high-leverage, token-burn-safe + +## Intake command + +- Job: `intake-audit-komandozentral` +- Project: `KomandoZentral` +- Path/scope: `/home/smlflg/Projekte/KomandoZentral` +- Mode: `review_only` + +## Safety + +- Review-only by default. +- No source project modifications. +- No secrets, commits, pushes, deletes, or automatic issue creation. + +## Expected artifacts + +- `jobs/done/intake-audit-komandozentral/result.json` +- `jobs/done/intake-audit-komandozentral/audit.md` + +## Verifier + +`python3 verifier/verify_artifacts.py --job jobs/pending/intake-audit-komandozentral.json --require-done` diff --git a/ProjectIntakeTower/github/issue_drafts/intake-build-verifier-hermes-profile-health.md b/ProjectIntakeTower/github/issue_drafts/intake-build-verifier-hermes-profile-health.md new file mode 100644 index 0000000000000000000000000000000000000000..8515ce35c021728206b6d4fc05a82d52aec6aa3d --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/intake-build-verifier-hermes-profile-health.md @@ -0,0 +1,25 @@ +# [ProjectIntakeTower] Run and improve the ProjectIntakeTower Hermes profile health verifier; summarize unhealthy profiles and safe next actions. + +Labels: intake, agent-job, read-only, verifier, high-leverage, token-burn-safe + +## Intake command + +- Job: `intake-build-verifier-hermes-profile-health` +- Project: `Hermes profile health` +- Path/scope: `/home/smlflg/.hermes/profiles` +- Mode: `review_only` + +## Safety + +- Review-only by default. +- No source project modifications. +- No secrets, commits, pushes, deletes, or automatic issue creation. + +## Expected artifacts + +- `jobs/done/intake-build-verifier-hermes-profile-health/result.json` +- `jobs/done/intake-build-verifier-hermes-profile-health/hermes_profile_health_summary.md` + +## Verifier + +`python3 verifier/verify_artifacts.py --job jobs/pending/intake-build-verifier-hermes-profile-health.json --require-done` diff --git a/ProjectIntakeTower/github/issue_drafts/intake-consolidate-agent-control-tower-repos.md b/ProjectIntakeTower/github/issue_drafts/intake-consolidate-agent-control-tower-repos.md new file mode 100644 index 0000000000000000000000000000000000000000..ef7e9e4ef1091ac3def9974b3df98514432cb756 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/intake-consolidate-agent-control-tower-repos.md @@ -0,0 +1,26 @@ +# [ProjectIntakeTower] Consolidate the Agent Control Tower family conceptually: map overlaps, pick system of record candidates, and propose merge/archive sequence. No repo edits. + +Labels: intake, agent-job, read-only, consolidation, needs-human, high-leverage, token-burn-safe + +## Intake command + +- Job: `intake-consolidate-agent-control-tower-repos` +- Project: `Agent Control Tower repos` +- Path/scope: `/home/smlflg/Projekte` +- Mode: `review_only` + +## Safety + +- Review-only by default. +- No source project modifications. +- No secrets, commits, pushes, deletes, or automatic issue creation. + +## Expected artifacts + +- `jobs/done/intake-consolidate-agent-control-tower-repos/result.json` +- `jobs/done/intake-consolidate-agent-control-tower-repos/consolidation_matrix.md` +- `jobs/done/intake-consolidate-agent-control-tower-repos/owner_decision_tree.md` + +## Verifier + +`python3 verifier/verify_artifacts.py --job jobs/pending/intake-consolidate-agent-control-tower-repos.json --require-done` diff --git a/ProjectIntakeTower/github/issue_drafts/intake-generate-tests-werbinich.md b/ProjectIntakeTower/github/issue_drafts/intake-generate-tests-werbinich.md new file mode 100644 index 0000000000000000000000000000000000000000..066e95d5bbc56766208ceecd734f289da3402957 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/intake-generate-tests-werbinich.md @@ -0,0 +1,26 @@ +# [ProjectIntakeTower] Generate a test plan and ready-to-apply test patch for WerBinIch without editing the source repo. + +Labels: intake, agent-job, read-only, test-generation, high-leverage, token-burn-safe + +## Intake command + +- Job: `intake-generate-tests-werbinich` +- Project: `WerBinIch` +- Path/scope: `/home/smlflg/Projekte/WerBinIch` +- Mode: `review_only` + +## Safety + +- Review-only by default. +- No source project modifications. +- No secrets, commits, pushes, deletes, or automatic issue creation. + +## Expected artifacts + +- `jobs/done/intake-generate-tests-werbinich/result.json` +- `jobs/done/intake-generate-tests-werbinich/test_plan.md` +- `jobs/done/intake-generate-tests-werbinich/proposed_tests.patch` + +## Verifier + +`python3 verifier/verify_artifacts.py --job jobs/pending/intake-generate-tests-werbinich.json --require-done` diff --git a/ProjectIntakeTower/github/issue_drafts/luishandoff-c8c475f685.md b/ProjectIntakeTower/github/issue_drafts/luishandoff-c8c475f685.md new file mode 100644 index 0000000000000000000000000000000000000000..2b3cf489701aa2afc2b12696e15cafba02f5a25f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/luishandoff-c8c475f685.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] LuisHandoff: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/LuisHandoff` +- Status: `needs_human` +- Score: `49` +- Risk: `medium` +- Technologies: unknown +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/luishandoff-c8c475f685.md` +- Evidence file: `inventory/evidence/luishandoff-c8c475f685.json` +- TODO/FIXME/WIP hints: 17 +- Plan hits: 4 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-luishandoff-c8c475f685-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/megaHarness/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/megaHarness/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..00757ec01540e8511e2157abe1d77d2b64f55f3d --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/megaHarness/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for megaHarness +Repo: https://github.com/smlfg/MegaHarness.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/megaHarness` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/openclaude/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/openclaude/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..906fbe797a1e5a72b6887d137aa65317057d6977 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/openclaude/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for openclaude +Repo: https://github.com/Gitlawb/openclaude +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/derWolfimSchafspelz/openclaude` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/portfoliotimeline-74850fb9b9.md b/ProjectIntakeTower/github/issue_drafts/portfoliotimeline-74850fb9b9.md new file mode 100644 index 0000000000000000000000000000000000000000..92fd34189fb62214dde6a871d39632044a87ed18 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/portfoliotimeline-74850fb9b9.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] PortfolioTimeline: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/PortfolioTimeline` +- Status: `needs_human` +- Score: `52` +- Risk: `medium` +- Technologies: unknown +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/portfoliotimeline-74850fb9b9.md` +- Evidence file: `inventory/evidence/portfoliotimeline-74850fb9b9.json` +- TODO/FIXME/WIP hints: 29 +- Plan hits: 7 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-portfoliotimeline-74850fb9b9-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/ra/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/ra/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..f1c7c65735a67b800d3398e7d78f1ed54b338b10 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ra/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for ra +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.hermes/profiles/ra` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/samuel-os-v2/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/samuel-os-v2/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..7fb78213535096d93de9324437fba0662670a434 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/samuel-os-v2/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for samuel-os-v2 +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/samuel-os-v2` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/schloss_PDF/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/schloss_PDF/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..2af1cb59e67a58b5f8fc2f61a2bb23d822de1c23 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/schloss_PDF/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for schloss_PDF +Repo: NEEDS_REPO_MAPPING +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/Projekte/schloss_PDF` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/shortcutcounter-d2ffa4d801.md b/ProjectIntakeTower/github/issue_drafts/shortcutcounter-d2ffa4d801.md new file mode 100644 index 0000000000000000000000000000000000000000..f988d8edcf05c8c724577543aea09210cb0237e9 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/shortcutcounter-d2ffa4d801.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] ShortcutCounter: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/ShortcutCounter` +- Status: `active` +- Score: `51` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 2 + +## Evidence + +- Project card: `inventory/project_cards/shortcutcounter-d2ffa4d801.md` +- Evidence file: `inventory/evidence/shortcutcounter-d2ffa4d801.json` +- TODO/FIXME/WIP hints: 8 +- Plan hits: 1 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-shortcutcounter-d2ffa4d801-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-93e2e4592e.md b/ProjectIntakeTower/github/issue_drafts/sidecar-93e2e4592e.md new file mode 100644 index 0000000000000000000000000000000000000000..5f01fe0787f68c6d46e1c31c1d56d37d81a35d2f --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-93e2e4592e.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar` +- Status: `active` +- Score: `63` +- Risk: `medium` +- Technologies: docs/notes +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-93e2e4592e.md` +- Evidence file: `inventory/evidence/sidecar-93e2e4592e.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 4 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-93e2e4592e-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-ng-6382aa0e95.md b/ProjectIntakeTower/github/issue_drafts/sidecar-ng-6382aa0e95.md new file mode 100644 index 0000000000000000000000000000000000000000..de75856d302c4212d9238dbc429baf1896572024 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-ng-6382aa0e95.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-ng: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-ng` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: docs/notes +- Git dirty tracked files: 6 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-ng-6382aa0e95.md` +- Evidence file: `inventory/evidence/sidecar-ng-6382aa0e95.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-ng-6382aa0e95-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v5-ee6c377f82.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v5-ee6c377f82.md new file mode 100644 index 0000000000000000000000000000000000000000..25ca4bd5ba1dda2458d7a5d49cb7442cb9f2d841 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v5-ee6c377f82.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V5: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V5` +- Status: `active` +- Score: `58` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v5-ee6c377f82.md` +- Evidence file: `inventory/evidence/sidecar-v5-ee6c377f82.json` +- TODO/FIXME/WIP hints: 12 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v5-ee6c377f82-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v6-bf4e8dc3cb.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v6-bf4e8dc3cb.md new file mode 100644 index 0000000000000000000000000000000000000000..0ec82bcc8bde1b622245fd625820d065715ad074 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v6-bf4e8dc3cb.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V6: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V6` +- Status: `active` +- Score: `56` +- Risk: `low` +- Technologies: agent, python +- Git dirty tracked files: 0 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v6-bf4e8dc3cb.md` +- Evidence file: `inventory/evidence/sidecar-v6-bf4e8dc3cb.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 7 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v6-bf4e8dc3cb-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v7-ed034c870d.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v7-ed034c870d.md new file mode 100644 index 0000000000000000000000000000000000000000..b676be3d80340ea64cc3bca9879fb8e18e0c8926 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v7-ed034c870d.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V7: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7` +- Status: `active` +- Score: `77` +- Risk: `medium` +- Technologies: agent, python +- Git dirty tracked files: 5 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v7-ed034c870d.md` +- Evidence file: `inventory/evidence/sidecar-v7-ed034c870d.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 8 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v7-ed034c870d-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v7-lite-323322aa5b.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v7-lite-323322aa5b.md new file mode 100644 index 0000000000000000000000000000000000000000..780e5f02d10528cac9d7aea8c1dd5fcd9dbc2e19 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v7-lite-323322aa5b.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V7-Lite: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V7-Lite` +- Status: `needs_human` +- Score: `37` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 2 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v7-lite-323322aa5b.md` +- Evidence file: `inventory/evidence/sidecar-v7-lite-323322aa5b.json` +- TODO/FIXME/WIP hints: 4 +- Plan hits: 1 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v7-lite-323322aa5b-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v8-9f03a02b07.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v8-9f03a02b07.md new file mode 100644 index 0000000000000000000000000000000000000000..2ac4bbcad4156572d0c345dd48187ba25dd00576 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v8-9f03a02b07.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V8: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8` +- Status: `active` +- Score: `60` +- Risk: `medium` +- Technologies: agent, python +- Git dirty tracked files: 7 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v8-9f03a02b07.md` +- Evidence file: `inventory/evidence/sidecar-v8-9f03a02b07.json` +- TODO/FIXME/WIP hints: 8 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v8-9f03a02b07-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/sidecar-v8-plan-d6f06ac5d8.md b/ProjectIntakeTower/github/issue_drafts/sidecar-v8-plan-d6f06ac5d8.md new file mode 100644 index 0000000000000000000000000000000000000000..b1a21f62e439849b0f6a122f4207eb0479c85abc --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/sidecar-v8-plan-d6f06ac5d8.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Sidecar-V8-Plan: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: docs/notes +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/sidecar-v8-plan-d6f06ac5d8.md` +- Evidence file: `inventory/evidence/sidecar-v8-plan-d6f06ac5d8.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-sidecar-v8-plan-d6f06ac5d8-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/ueber_agent-8860cb125d.md b/ProjectIntakeTower/github/issue_drafts/ueber_agent-8860cb125d.md new file mode 100644 index 0000000000000000000000000000000000000000..7cb93b7086bcc138ac9696bf45d4f189b7a30c36 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/ueber_agent-8860cb125d.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] UEBER_AGENT: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/UEBER_AGENT` +- Status: `active` +- Score: `68` +- Risk: `medium` +- Technologies: docs/notes +- Git dirty tracked files: 17 + +## Evidence + +- Project card: `inventory/project_cards/ueber_agent-8860cb125d.md` +- Evidence file: `inventory/evidence/ueber_agent-8860cb125d.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 9 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-ueber_agent-8860cb125d-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/visual-explainer/intake-next-action.md b/ProjectIntakeTower/github/issue_drafts/visual-explainer/intake-next-action.md new file mode 100644 index 0000000000000000000000000000000000000000..44ef1742dfec8ab09aeb9d973c67340183e38f12 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/visual-explainer/intake-next-action.md @@ -0,0 +1,16 @@ +Title: Intake: next action for visual-explainer +Repo: https://github.com/nicobailon/visual-explainer.git +Labels: intake:discovered,agent:handoff-ready + +## Evidence + +- Path: `/home/smlflg/.hermes/skills/visual-explainer` +- Status: quick_win +- TODO count: 0 +- Verification: passed + +## Acceptance criteria + +- One concrete next action selected. +- Verifier command documented. +- No secrets exposed. diff --git a/ProjectIntakeTower/github/issue_drafts/werbinich-4b2f31741d.md b/ProjectIntakeTower/github/issue_drafts/werbinich-4b2f31741d.md new file mode 100644 index 0000000000000000000000000000000000000000..c1d6886d683ad069c9b2ad961c9fe493ce99cbb0 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/werbinich-4b2f31741d.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] WerBinIch: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/WerBinIch` +- Status: `active` +- Score: `59` +- Risk: `medium` +- Technologies: python +- Git dirty tracked files: 1 + +## Evidence + +- Project card: `inventory/project_cards/werbinich-4b2f31741d.md` +- Evidence file: `inventory/evidence/werbinich-4b2f31741d.json` +- TODO/FIXME/WIP hints: 20 +- Plan hits: 0 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-werbinich-4b2f31741d-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/issue_drafts/zentrale-193cdb6361.md b/ProjectIntakeTower/github/issue_drafts/zentrale-193cdb6361.md new file mode 100644 index 0000000000000000000000000000000000000000..e9ebfef5d00b4449118e46135e66aa7b9c980a83 --- /dev/null +++ b/ProjectIntakeTower/github/issue_drafts/zentrale-193cdb6361.md @@ -0,0 +1,32 @@ +# [ProjectIntakeTower] Zentrale: bounded read-only handoff + +## Project + +- Path: `/home/smlflg/Projekte/Zentrale` +- Status: `active` +- Score: `70` +- Risk: `medium` +- Technologies: agent, python +- Git dirty tracked files: 19 + +## Evidence + +- Project card: `inventory/project_cards/zentrale-193cdb6361.md` +- Evidence file: `inventory/evidence/zentrale-193cdb6361.json` +- TODO/FIXME/WIP hints: 40 +- Plan hits: 1 + +## Proposed next action + +Run the bounded review-only job and produce `result.json` plus `handoff.md`. Do not modify the source project from this intake issue. + +## Bounded job + +- `jobs/pending/pit-zentrale-193cdb6361-review.json` + +## Acceptance criteria + +- One concrete next action is selected. +- Any human gate is explicit. +- Verifier command/result is documented. +- No secrets or source-project modifications. diff --git a/ProjectIntakeTower/github/labels.md b/ProjectIntakeTower/github/labels.md new file mode 100644 index 0000000000000000000000000000000000000000..1b4dcf6af5011b70ab5878f4a93dd95a51f1fc43 --- /dev/null +++ b/ProjectIntakeTower/github/labels.md @@ -0,0 +1,29 @@ +# GitHub Labels + +Canonical labels for ProjectIntakeTower intake drafts/jobs: + +- `intake` — Generated or managed by ProjectIntakeTower intake workflow. +- `agent-job` — Has a bounded worker/job contract with artifact duty. +- `read-only` — Source projects must not be modified by this task. +- `test-generation` — Produces tests or test patches, not applied automatically. +- `verifier` — Builds, runs, or improves verification artifacts. +- `consolidation` — Compares overlapping repos and proposes a consolidation path. +- `archive-candidate` — Candidate for archive/no-action review; never delete automatically. +- `needs-human` — Requires owner decision before execution or source mutation. +- `high-leverage` — Expected to reduce many open loops or unblock multiple projects. +- `token-burn-safe` — Bounded to local artifacts and concise evidence to avoid runaway context/token use. + +## Legacy/generated aliases still accepted + +- `intake:discovered` +- `intake:todo` +- `intake:verification-failed` +- `intake:quick-win` +- `intake:needs-human` +- `intake:archive-candidate` +- `intake:merge-candidate` +- `agent:handoff-ready` +- `priority:p0` +- `priority:p1` +- `priority:p2` +- `priority:p3` diff --git a/ProjectIntakeTower/inventory/evidence/a_lite-cd34b17e00.json b/ProjectIntakeTower/inventory/evidence/a_lite-cd34b17e00.json new file mode 100644 index 0000000000000000000000000000000000000000..5aa53a8512038c28a218e91827471d38cf62450d --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/a_lite-cd34b17e00.json @@ -0,0 +1,138 @@ +{ + "project_id": "a_lite-cd34b17e00", + "path": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite", + "readme_path": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/README.md", + "readme_summary": "# Pfad A Lite — Kommandozentrale ## Aktueller Integrationsstatus `A_lite` ist im Repo bereits als echter Pfad vorbereitet. Im aktuellen Stern-Stand ist `A_lite` aber noch **nicht** als aktiver `stern1`-Zielpfad freigegeben. Der Grund ist nicht inhaltlich, sondern technisch-operativ: - die Agenten und das Deployskript existieren - die Session-Strategie fuer `stern1 -> router_a` ist noch nicht als belastbarer Produktionspfad validiert Solange diese Freigabe fehlt, gilt:", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 14, + "text": "- [ ] Routing-Schema definieren (welche msg_types?)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 15, + "text": "- [ ] SternMessage-Schema festlegen (max 5-6 msg_types)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 16, + "text": "- [ ] Mini-CWM Session-State im Router" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 17, + "text": "- [ ] Triage-Logik spezifizieren" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 18, + "text": "- [ ] Tracing-Format definieren" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 115, + "text": "Der Router gibt `[ROUTE: xxx]` aus. Das Gateway muss das parsen." + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 199, + "text": "- Nach 50 Messages: Review die Fehler" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 234, + "text": "8. **Output-Parsing?** Wie fängt das Gateway `[ROUTE: xxx]` ab?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 241, + "text": "- [ ] SternMessage-Schema definiert (max 5-6 msg_types)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 242, + "text": "- [ ] Mini-CWM Session-State im Router spezifiziert" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 243, + "text": "- [ ] Routing-Schema festgelegt" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 244, + "text": "- [ ] Tracing-Format definiert" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 245, + "text": "- [ ] Heterogene Modell-Auswahl pro Pfad geklärt" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 248, + "text": "- [ ] Agents registriert und erreichbar?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 249, + "text": "- [ ] Gateway bindet an router_a?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 252, + "text": "- [ ] Delegation funktioniert?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 255, + "text": "- [ ] Alle 4 Routing-Fälle korrekt?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md", + "line": 258, + "text": "- [ ] Routing-Genauigkeit > 80%?" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/deploy_path_a.sh", + "line": 53, + "text": "echo \"Manual next steps:\"" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/HARNESS_SPEC.md", + "line": 141, + "text": "- [ ] Message Schema final abnehmen" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/HARNESS_SPEC.md", + "line": 142, + "text": "- [ ] Confidence-Scores kalibrieren (wo ist die Schwelle?)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/HARNESS_SPEC.md", + "line": 143, + "text": "- [ ] Max history Länge (5 oder 3?)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/HARNESS_SPEC.md", + "line": 144, + "text": "- [ ] Wie werden corrections gespeichert? (In-Memory, Datei, DB?)" + }, + { + "file": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_research.md", + "line": 29, + "text": "- Suchst nach aktuellen Open-Source LLMs (Mistral, Llama, Phi, etc.)" + } + ], + "plan_hits": [ + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/BUILD_PLAN.md" + ], + "agent_artifacts": [ + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/router_a/AGENTS.md", + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_private/AGENTS.md", + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_research/AGENTS.md", + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_builder/AGENTS.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-09c87d8044.json b/ProjectIntakeTower/inventory/evidence/aaai2026-09c87d8044.json new file mode 100644 index 0000000000000000000000000000000000000000..2ea6ac1f399b4a2f2a521d5d0bd4ef52ba3d25cb --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-09c87d8044.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-09c87d8044", + "path": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-1ad8d21da1.json b/ProjectIntakeTower/inventory/evidence/aaai2026-1ad8d21da1.json new file mode 100644 index 0000000000000000000000000000000000000000..c9b8e9eb841bc7a86214a77012700b31c26dc021 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-1ad8d21da1.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-1ad8d21da1", + "path": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-39414e3233.json b/ProjectIntakeTower/inventory/evidence/aaai2026-39414e3233.json new file mode 100644 index 0000000000000000000000000000000000000000..e1442e383c651c4407e36722fff5048ab2dd7309 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-39414e3233.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-39414e3233", + "path": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-436510c28c.json b/ProjectIntakeTower/inventory/evidence/aaai2026-436510c28c.json new file mode 100644 index 0000000000000000000000000000000000000000..944c72b6bcb8e705526feb69fb666ac7e4bf89ba --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-436510c28c.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-436510c28c", + "path": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-5a381067f9.json b/ProjectIntakeTower/inventory/evidence/aaai2026-5a381067f9.json new file mode 100644 index 0000000000000000000000000000000000000000..14f931df0571c2155075313850f0707b39fa4626 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-5a381067f9.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-5a381067f9", + "path": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-7ef6f11603.json b/ProjectIntakeTower/inventory/evidence/aaai2026-7ef6f11603.json new file mode 100644 index 0000000000000000000000000000000000000000..10d7bb3322f04c562328bc2b38b621cec31638b1 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-7ef6f11603.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-7ef6f11603", + "path": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-d84af33260.json b/ProjectIntakeTower/inventory/evidence/aaai2026-d84af33260.json new file mode 100644 index 0000000000000000000000000000000000000000..6f1a9da179f0e503c2510e46baa74cee12712c90 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-d84af33260.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-d84af33260", + "path": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-f974266cb1.json b/ProjectIntakeTower/inventory/evidence/aaai2026-f974266cb1.json new file mode 100644 index 0000000000000000000000000000000000000000..05145d62a0d9764b4b77d4a12404757820c82758 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-f974266cb1.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-f974266cb1", + "path": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/aaai2026-fdeb41c324.json b/ProjectIntakeTower/inventory/evidence/aaai2026-fdeb41c324.json new file mode 100644 index 0000000000000000000000000000000000000000..f88edfd13078ac29cabd2732fc3e7d91d3fd185f --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/aaai2026-fdeb41c324.json @@ -0,0 +1,216 @@ +{ + "project_id": "aaai2026-fdeb41c324", + "path": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026", + "readme_path": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "readme_summary": "# AAAI 2026 统一LaTeX模板使用说明 / AAAI 2026 Unified LaTeX Template Guide > **📝 重要说明 / Important Notice**: 本仓库借助Cursor在AAAI 2026官方模板基础上改进得到。如果遇到不满足或有冲突的情况,请积极提issues。 > > **📝 Important Notice**: This repository is improved based on the official AAAI 2026 template with the assistance of Cursor. If you encounter any issues or conflicts, please actively submit issues. [中文](#中文版本) | [English](#english-version) --- ## 🌐 在线查看 / Online Access **📖 在线阅读和测试模板**: [https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07](https://cn.overleaf.com/read/wyhcnvcrtpyt#cd4a07)", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 158, + "text": "- [ ] 已设置 `\\def\\aaaianonymous{true}` (匿名投稿)" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 159, + "text": "- [ ] 已注释掉所有可能暴露身份的信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 160, + "text": "- [ ] 已匿名化参考文献(移除作者姓名)" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 163, + "text": "- [ ] 标题、摘要、关键词已填写" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 164, + "text": "- [ ] 所有章节内容完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 165, + "text": "- [ ] 图表编号连续且正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 166, + "text": "- [ ] 参考文献格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 167, + "text": "- [ ] 补充材料(如有)已准备" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 170, + "text": "- [ ] 页面边距符合要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 171, + "text": "- [ ] 字体和字号正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 172, + "text": "- [ ] 行间距符合标准" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 173, + "text": "- [ ] 图表位置和大小合适" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 174, + "text": "- [ ] 数学公式格式正确" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 177, + "text": "- [ ] LaTeX编译无错误" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 178, + "text": "- [ ] 参考文献正确生成" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 179, + "text": "- [ ] PDF输出正常" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 180, + "text": "- [ ] 文件大小在限制范围内" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 185, + "text": "- [ ] 已注释掉 `\\def\\aaaianonymous{true}` (camera-ready)" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 186, + "text": "- [ ] 已添加完整的作者信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 187, + "text": "- [ ] 已添加所有作者单位信息" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 188, + "text": "- [ ] 已恢复所有被注释的内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 191, + "text": "- [ ] 已根据审稿意见修改内容" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 192, + "text": "- [ ] 已更新所有图表和实验" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 193, + "text": "- [ ] 已完善补充材料" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 194, + "text": "- [ ] 已检查所有链接和引用" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 197, + "text": "- [ ] 最终PDF质量检查" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 198, + "text": "- [ ] 所有文件已备份" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 199, + "text": "- [ ] 符合会议最终提交要求" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 200, + "text": "- [ ] 补充材料已单独提交(如需要)" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 205, + "text": "- [ ] 补充材料与主论文内容对应" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 206, + "text": "- [ ] 章节结构清晰合理" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 207, + "text": "- [ ] 图表编号与主论文不冲突" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 208, + "text": "- [ ] 参考文献格式一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 211, + "text": "- [ ] 算法伪代码清晰完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 212, + "text": "- [ ] 实验设置详细说明" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 213, + "text": "- [ ] 数据预处理步骤明确" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 214, + "text": "- [ ] 超参数配置完整" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 217, + "text": "- [ ] 使用统一的supp模板" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 218, + "text": "- [ ] 页面设置与主论文一致" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md", + "line": 219, + "text": "- [ ] 字体和格式符合要求" + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-template.tex", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/aaai2026-unified-supp.tex", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/aaai2026.sty", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/aaai2026/README.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-0ab26d6784.json b/ProjectIntakeTower/inventory/evidence/acl-0ab26d6784.json new file mode 100644 index 0000000000000000000000000000000000000000..8801d274605bf2c509c2a5a38e75fd622126e171 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-0ab26d6784.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-0ab26d6784", + "path": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/diagnosis/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-2812c1f3f2.json b/ProjectIntakeTower/inventory/evidence/acl-2812c1f3f2.json new file mode 100644 index 0000000000000000000000000000000000000000..583ebfb84acda2cfd94f96258a8b54fe1c260033 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-2812c1f3f2.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-2812c1f3f2", + "path": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/dlm/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-4b04c643d7.json b/ProjectIntakeTower/inventory/evidence/acl-4b04c643d7.json new file mode 100644 index 0000000000000000000000000000000000000000..aaa169dcd972876164ecd56aa841bdae43fa9d92 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-4b04c643d7.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-4b04c643d7", + "path": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/ra/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-4e6870f154.json b/ProjectIntakeTower/inventory/evidence/acl-4e6870f154.json new file mode 100644 index 0000000000000000000000000000000000000000..f86d8fe7ef3d165ee00e4a6b826cf3f0ff2a3533 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-4e6870f154.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-4e6870f154", + "path": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/mlg/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-8c8fc6cd3f.json b/ProjectIntakeTower/inventory/evidence/acl-8c8fc6cd3f.json new file mode 100644 index 0000000000000000000000000000000000000000..514edb9518ae4aa89c02d7442eec1fab394571c7 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-8c8fc6cd3f.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-8c8fc6cd3f", + "path": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/voice-learning/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-95289e4e2c.json b/ProjectIntakeTower/inventory/evidence/acl-95289e4e2c.json new file mode 100644 index 0000000000000000000000000000000000000000..b297c79fb6c7a93f514b7a7ddccb0502bbd03b6c --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-95289e4e2c.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-95289e4e2c", + "path": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/decision-control/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-bba97c8888.json b/ProjectIntakeTower/inventory/evidence/acl-bba97c8888.json new file mode 100644 index 0000000000000000000000000000000000000000..f39c6abff4decd8e2dc2a86986e31763010f815c --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-bba97c8888.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-bba97c8888", + "path": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/fixer/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-c178e84d62.json b/ProjectIntakeTower/inventory/evidence/acl-c178e84d62.json new file mode 100644 index 0000000000000000000000000000000000000000..aa8ed5aa4e5bb8f6b5f907f29fbd93b960c370be --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-c178e84d62.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-c178e84d62", + "path": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/openclaude-mcp/skills/research/research-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acl-c3fe5fa952.json b/ProjectIntakeTower/inventory/evidence/acl-c3fe5fa952.json new file mode 100644 index 0000000000000000000000000000000000000000..7ced845d250b31bc6b1e9f14cffd472ca27bb5d7 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acl-c3fe5fa952.json @@ -0,0 +1,115 @@ +{ + "project_id": "acl-c3fe5fa952", + "path": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl", + "readme_path": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/README.md", + "readme_summary": "# *ACL Paper Styles This directory contains the latest LaTeX templates for *ACL conferences. ## Instructions for authors Paper submissions to *ACL conferences must use the official ACL style templates. The LaTeX style files are available - as an [Overleaf template](https://www.overleaf.com/latex/templates/association-for-computational-linguistics-acl-conference/jvxskxpnznfj) - in this repository", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 3, + "text": "The following instructions are for authors of papers submitted for review to ACL conferences (hereafter, \"review version\") or paper accepted for publication in its proceedings (hereafter, \"final version\")." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 17, + "text": "Review versions of long papers may have up to eight (8) pages of content plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 19, + "text": "Review versions of short papers may have up to four (4) pages of content, plus unlimited pages for references." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 23, + "text": "The conference encourages submission of appendices and supplementary material, which are not required to fit within these page limits. However, review versions of papers must be self-contained: it is optional for reviewers to look at appendices or supplementar" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 25, + "text": "Review versions should not refer, for further detail, to documents, code or data resources that are not available to the reviewers." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 27, + "text": "Papers that do not conform to these requirements may be rejected without review." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 34, + "text": "As reviewing will be double-blind, review versions must not include any identifying information about the authors (such as names, affiliations, or URLs)." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 47, + "text": "Review versions must not include acknowledgements." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 49, + "text": "**Papers that do not conform to these requirements may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 51, + "text": "Any preliminary non-archival versions of submitted papers should be listed in the submission form but not in the review version of the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 87, + "text": "Review versions should have page numbers, centered in the bottom margin, but **pages should not be numbered in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 102, + "text": "In the review version, a ruler (line numbers in the left and right margins of the article) should be printed, so that reviewers may comment on particular lines in the paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 147, + "text": "**Even in the review version of the paper, you should maintain space for names and addresses so that they will fit in the final version.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 244, + "text": "Do not include this section in the review version." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 290, + "text": "Review versions of appendices must follow the same anonymity guidelines as the main paper." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 295, + "text": "Any accompanying software and/or data should include licenses and documentation of research review as appropriate." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 300, + "text": "**Submissions that misuse the supplementary material may be rejected without review.**" + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 304, + "text": "The paper should not rely on the supplementary material: while the paper may refer to and cite the supplementary material and the supplementary material will be available to the reviewers, they will not be asked to review the supplementary material." + }, + { + "file": "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "line": 306, + "text": "Review versions of supplementary material must follow the same anonymity guidelines as the main paper." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/acl_latex.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/acl_lualatex.tex", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/formatting.md", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/custom.bib", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/README.md", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/acl_natbib.bst", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/anthology.bib.txt", + "/home/smlflg/.hermes/profiles/ra/skills/research/ml-paper-writing/templates/acl/acl.sty" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/acpcodex-c949d6755e.json b/ProjectIntakeTower/inventory/evidence/acpcodex-c949d6755e.json new file mode 100644 index 0000000000000000000000000000000000000000..8acde5d60a6a1bd74ae539b760b9ab9c17cb2369 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/acpcodex-c949d6755e.json @@ -0,0 +1,35 @@ +{ + "project_id": "acpcodex-c949d6755e", + "path": "/home/smlflg/Projekte/ACPcodex", + "readme_path": "/home/smlflg/Projekte/ACPcodex/README.md", + "readme_summary": "# ACP Codex Subagents This workspace turns the `idea` note into a small runnable ACP/Codex orchestration layer. It uses `acpx` named sessions as the transport and keeps each subagent scoped by role and file ownership. `acpx` is still alpha, so this is an experimental workflow. The script defaults to `npx -y acpx@latest` when a global `acpx` binary is not installed. ## Quick Start Check the local prerequisites:", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/Projekte/ACPcodex/README.md", + "line": 33, + "text": "./scripts/acpx-subagents parallel --no-wait -- \"Review your owned area and report the smallest safe implementation plan.\"" + }, + { + "file": "/home/smlflg/Projekte/ACPcodex/scripts/acpx-subagents", + "line": 18, + "text": "[ui]=\"Implement and review user-facing UI, templates, static assets, and component behavior.\"" + }, + { + "file": "/home/smlflg/Projekte/ACPcodex/scripts/acpx-subagents", + "line": 19, + "text": "[pipeline]=\"Implement and review pipeline flow, runtime behavior, schemas, and guard logic.\"" + }, + { + "file": "/home/smlflg/Projekte/ACPcodex/scripts/acpx-subagents", + "line": 20, + "text": "[rules]=\"Implement and review rule packs, policy definitions, validation behavior, and rule docs.\"" + } + ], + "plan_hits": [ + "/home/smlflg/Projekte/ACPcodex/idea" + ], + "agent_artifacts": [ + "/home/smlflg/Projekte/ACPcodex/.codex" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/act-agentcommandotower-0112bb030d.json b/ProjectIntakeTower/inventory/evidence/act-agentcommandotower-0112bb030d.json new file mode 100644 index 0000000000000000000000000000000000000000..ed72f6856bc52c80bbbc39f0465b9230b5578d8d --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/act-agentcommandotower-0112bb030d.json @@ -0,0 +1,108 @@ +{ + "project_id": "act-agentcommandotower-0112bb030d", + "path": "/home/smlflg/Projekte/ACT-agentcommandotower", + "readme_path": "/home/smlflg/Projekte/ACT-agentcommandotower/README.md", + "readme_summary": "# commando-tower-v0 Minimal local operator cockpit for agentic projects. ## Commands ```bash python tower.py status python tower.py focus python tower.py add-decision \"\" python tower.py add-run --project X --harness Y --goal Z", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENT_JOB_TEMPLATE.md", + "line": 28, + "text": "- Open a pull request from a dedicated branch." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/README.md", + "line": 20, + "text": "Issue -> Branch -> Artifact -> Tests -> PR -> Review" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/README.md", + "line": 29, + "text": "- `.github/PULL_REQUEST_TEMPLATE.md` for PR review boundaries" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/README.md", + "line": 48, + "text": "3. Open a scoped issue from `.github/ISSUE_TEMPLATE/agent_job.yml`." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/decisions.md", + "line": 3, + "text": "- [ ] Pick next manual step" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/tower.py", + "line": 81, + "text": "print(\"Next action\")" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/tower.py", + "line": 88, + "text": "state[\"next_action\"] = f\"Review active runs and decisions for {args.project}\"" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/tower.py", + "line": 96, + "text": "with DECISIONS.open(\"a\") as file:" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENTS.md", + "line": 17, + "text": "- Create audit, test, review, decision, and risk artifacts." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENTS.md", + "line": 23, + "text": "- Store review artifacts under `artifacts/issue-/` so parallel agent runs do not collide." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENTS.md", + "line": 27, + "text": "- No open-ended feature building." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENTS.md", + "line": 40, + "text": "- Open risks" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENT_RESULT_TEMPLATE.md", + "line": 44, + "text": "Known residual risks, missing tests, and behavior that still needs owner review." + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENT_RESULT_TEMPLATE.md", + "line": 52, + "text": "- [ ] Concrete next issue title and reason" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/AGENT_RESULT_TEMPLATE.md", + "line": 53, + "text": "- [ ] Concrete next issue title and reason" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/focus.md", + "line": 5, + "text": "Next action: Review active runs and decisions for test-project" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/scripts/ensure-agent-labels.sh", + "line": 18, + "text": "\"agent:review|fbca04|Review or adversarial analysis\"" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/.github/PULL_REQUEST_TEMPLATE.md", + "line": 33, + "text": "## Human Review Needed?" + }, + { + "file": "/home/smlflg/Projekte/ACT-agentcommandotower/.github/ISSUE_TEMPLATE/agent_job.yml", + "line": 43, + "text": "- Open a pull request from a dedicated branch." + } + ], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/Projekte/ACT-agentcommandotower/AGENTS.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/additional_dir-58286e47b9.json b/ProjectIntakeTower/inventory/evidence/additional_dir-58286e47b9.json new file mode 100644 index 0000000000000000000000000000000000000000..d95be18e0970e227b8482758fe63e7917937cb53 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/additional_dir-58286e47b9.json @@ -0,0 +1,10 @@ +{ + "project_id": "additional_dir-58286e47b9", + "path": "/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_62254c5202e80a68f4fe6572a2be46a3d953de1a/tests/admin_scripts/custom_templates/project_template/additional_dir", + "readme_path": null, + "readme_summary": "", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/additional_dir-cfc39b22c3.json b/ProjectIntakeTower/inventory/evidence/additional_dir-cfc39b22c3.json new file mode 100644 index 0000000000000000000000000000000000000000..b86f155d606ae385f20f32c155882902ea64b2e0 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/additional_dir-cfc39b22c3.json @@ -0,0 +1,10 @@ +{ + "project_id": "additional_dir-cfc39b22c3", + "path": "/home/smlflg/Projekte/FirstRealHarnessEvaluation_KarpathiesMD/results/repo_cache/django__django_bceadd2788dc2dad53eba0caae172bd8522fd483/tests/admin_scripts/custom_templates/project_template/additional_dir", + "readme_path": null, + "readme_summary": "", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent-process-dashboard-a212950668.json b/ProjectIntakeTower/inventory/evidence/agent-process-dashboard-a212950668.json new file mode 100644 index 0000000000000000000000000000000000000000..6d8b2024846614ccf237b50b9495f6f6adfb07df --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent-process-dashboard-a212950668.json @@ -0,0 +1,33 @@ +{ + "project_id": "agent-process-dashboard-a212950668", + "path": "/home/smlflg/Projekte/agent-process-dashboard", + "readme_path": "/home/smlflg/Projekte/agent-process-dashboard/README.md", + "readme_summary": "# Agent Process Dashboard Standalone GTK dashboard for local Linux agent-process fanout. The app is deliberately conservative: - Reads `/proc` directly. - Shows current-user process trees and agent/MCP bridge fanout. - Reports stale and cleanup candidates as a dry-run only. - Can send `SIGTERM` and, after a failed stop, `SIGKILL` only to current dry-run candidates after explicit confirmation and a fresh PID identity recheck.", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/Projekte/agent-process-dashboard/README.md", + "line": 12, + "text": "- Does not restart, renice, mutate configs, read process environments, or open a" + }, + { + "file": "/home/smlflg/Projekte/agent-process-dashboard/src/agent_process_dashboard/classifier.py", + "line": 92, + "text": "matched = next((marker for marker in markers if marker in text), None)" + }, + { + "file": "/home/smlflg/Projekte/agent-process-dashboard/src/agent_process_dashboard/actions.py", + "line": 71, + "text": "live = next((sample for sample in snapshot.processes if sample.pid == request.pid), None)" + }, + { + "file": "/home/smlflg/Projekte/agent-process-dashboard/src/agent_process_dashboard/actions.py", + "line": 94, + "text": "candidate = next(" + } + ], + "plan_hits": [ + "/home/smlflg/Projekte/agent-process-dashboard/IMPLEMENTATION_PLAN.md" + ], + "agent_artifacts": [], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent-runs-e6bd77181d.json b/ProjectIntakeTower/inventory/evidence/agent-runs-e6bd77181d.json new file mode 100644 index 0000000000000000000000000000000000000000..d0c9b7b14e13070dc2000bd011051771d920543b --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent-runs-e6bd77181d.json @@ -0,0 +1,10 @@ +{ + "project_id": "agent-runs-e6bd77181d", + "path": "/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/docs/evaluation/agent-runs", + "readme_path": "/home/smlflg/Projekte/Sidecar-Workspace/Sidecar-V8-Plan/docs/evaluation/agent-runs/README.md", + "readme_summary": "# Agent Run Artifacts Agent jobs created under the GH Token Furnace Harness write reviewable outputs here. Use this path shape: ```text docs/evaluation/agent-runs/YYYY-MM-DD/-/ ``` Every run must include `AGENT_RESULT.md`. Add mode-specific artifacts from", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent_builder-c49298be80.json b/ProjectIntakeTower/inventory/evidence/agent_builder-c49298be80.json new file mode 100644 index 0000000000000000000000000000000000000000..c9e2792c76e0388fb6229792d9ebdf4e3d5acc7a --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent_builder-c49298be80.json @@ -0,0 +1,12 @@ +{ + "project_id": "agent_builder-c49298be80", + "path": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_builder", + "readme_path": null, + "readme_summary": "", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_builder/AGENTS.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent_private-4da39ba612.json b/ProjectIntakeTower/inventory/evidence/agent_private-4da39ba612.json new file mode 100644 index 0000000000000000000000000000000000000000..3319a9289007d7252ecea08726dfa0017d0cbef0 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent_private-4da39ba612.json @@ -0,0 +1,12 @@ +{ + "project_id": "agent_private-4da39ba612", + "path": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_private", + "readme_path": null, + "readme_summary": "", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_private/AGENTS.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent_research-82f8c1b2e6.json b/ProjectIntakeTower/inventory/evidence/agent_research-82f8c1b2e6.json new file mode 100644 index 0000000000000000000000000000000000000000..84b46c33f58a122fd8c16c904f67c7b30def5745 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent_research-82f8c1b2e6.json @@ -0,0 +1,12 @@ +{ + "project_id": "agent_research-82f8c1b2e6", + "path": "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_research", + "readme_path": null, + "readme_summary": "", + "todo_fixme_snippets": [], + "plan_hits": [], + "agent_artifacts": [ + "/home/smlflg/Projekte/UEBER_AGENT/bau/A_lite/agent_research/AGENTS.md" + ], + "secret_policy": "secret-like filenames/content skipped; snippets capped" +} \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agent_results.json b/ProjectIntakeTower/inventory/evidence/agent_results.json new file mode 100644 index 0000000000000000000000000000000000000000..0637a088a01e8ddab3bf3fa98dbe804cbde1a0dc --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agent_results.json @@ -0,0 +1 @@ +[] \ No newline at end of file diff --git a/ProjectIntakeTower/inventory/evidence/agentarena-a78ddede96.json b/ProjectIntakeTower/inventory/evidence/agentarena-a78ddede96.json new file mode 100644 index 0000000000000000000000000000000000000000..49f1f77c72132e31504a0f5b761425159f046d47 --- /dev/null +++ b/ProjectIntakeTower/inventory/evidence/agentarena-a78ddede96.json @@ -0,0 +1,211 @@ +{ + "project_id": "agentarena-a78ddede96", + "path": "/home/smlflg/Projekte/AgentArena", + "readme_path": "/home/smlflg/Projekte/AgentArena/README.md", + "readme_summary": "# AgentArena Benchmark platform for comparing AI agents on real coding tasks. Agents solve tasks in isolated Docker sandboxes. Results land in a leaderboard with pass@k, cost, and speed metrics. ## Status MVP — core evaluation pipeline implemented, E2E Docker test pending. ## Run ```bash", + "todo_fixme_snippets": [ + { + "file": "/home/smlflg/Projekte/AgentArena/FOR_SMLFLG.md", + "line": 111, + "text": "## Was fehlt / Next Steps" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/FOR_SMLFLG.md", + "line": 113, + "text": "2. **Patch-Apply Bug** — Run #9 zeigt \"Patch failed to apply\" (untersuchen)" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/FOR_SMLFLG.md", + "line": 126, + "text": "- **Cross-Model-Review lohnt sich:** MiniMax + Codex haben 13 Findings geliefert, 5 Quick Wins sofort gefixt" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/voicelanguage_bug_en.yaml", + "line": 1, + "text": "slug: voicelanguage-bug-en" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/voicelanguage_bug_en.yaml", + "line": 2, + "text": "title: \"VoiceLanguage Config Bug — English Prompt E4\"" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/timeout_unit_bug.yaml", + "line": 1, + "text": "slug: timeout-unit-bug" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/timeout_unit_bug.yaml", + "line": 2, + "text": "title: \"Timeout Unit Bug — Domain Knowledge E_new_b\"" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/reviewmode_noedit.yaml", + "line": 4, + "text": "Review this code and report any issues you find. Do NOT make any changes." + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/enum_convention_bug.yaml", + "line": 1, + "text": "slug: enum-convention-bug" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/enum_convention_bug.yaml", + "line": 2, + "text": "title: \"Enum Case Bug — Domain Knowledge E_new_a\"" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/enum_convention_bug.yaml", + "line": 7, + "text": "Lies den Code und fix den Bug. Alle relevanten Dateien liegen im Projektverzeichnis." + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/implicit_null_bug.yaml", + "line": 1, + "text": "slug: implicit-null-bug" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/example_fix_bug.yaml", + "line": 6, + "text": "Fix the bug so all pagination tests pass." + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/example_fix_bug.yaml", + "line": 9, + "text": "ref: bug-branch-001" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/scope_creep.yaml", + "line": 4, + "text": "Die add-Funktion in calculator.py gibt falsche Ergebnisse. Fix den Bug." + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/voicelanguage_bug.yaml", + "line": 1, + "text": "slug: voicelanguage-bug" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/voicelanguage_bug.yaml", + "line": 2, + "text": "title: \"VoiceLanguage Config Bug — A/B Test E2\"" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/breaking_change_bug.yaml", + "line": 1, + "text": "slug: breaking-change-bug" + }, + { + "file": "/home/smlflg/Projekte/AgentArena/tasks/fix_off_by_one.yaml", + "line": 6, + "text": "(pages are 1-based). Fix the bug so all pagination tests pass." + }, + { + "file": "/home/smlflg/Projekte/AgentArena/templates/index.html", + "line": 12, + "text": "