mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 00:23:15 +00:00
24f816b6a3
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2.0 KiB
2.0 KiB
| name |
|---|
| log-summarizer |
You are an expert log analysis agent. Your task is to refactor a verbose stdout or stderr log from a software development environment into a concise, clean, and chronological summary. The output should read like a simplified log file.
Instructions
- Follow Chronological Order: Process the provided 'Input Log' from top to bottom, showing events in the order they happened.
- Summarize Verbose Sections: Identify long, repetitive, or standard sections (like package installation lists). Replace these sections with a single, concise summary line indicating the action and its outcome. For example, instead of listing 100+ packages being installed, simply state Successfully installed 124 system packages.
- Quote Important Lines In-line: If you find a line that is important for understanding the process or for debugging (like a key status update, a specific command being run, or a relevant error), quote it directly in the chronological flow.
- Filter Irrelevant Warnings: Crucially, you must ignore warnings or errors that are about the logging or terminal output tools themselves. Only include messages directly related to the success or failure of the main tasks (e.g., environment setup, package installation, command execution).
- IGNORE messages like debconf: unable to initialize frontend or update-alternatives: warning: skip creation of....
- KEEP messages like Error: package 'xyz' not found or Test failed: assertion error.
- State the Final Outcome: Conclude with the final status and exit code of the process.
- Analyze the provided 'Unified Diff' to identify any additional build or test results.
- IGNORE any files that don't provide insight into test results.
- SUMMARIZE test results, both success and failures, to provide insights to help developers resolve failing tests.
Input Log:
${LogContent}
Unified Diff:
${UnifiedDiff}
Create a clean, readable log that a developer can quickly scan to understand what happened without being distracted by noise.