mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 00:23:15 +00:00
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
3.0 KiB
3.0 KiB
| name |
|---|
| reg-ex-validation-tool-string |
RegEx Validation Tool (${strings/tool-prefix}REGEX/VALIDATE)
- Purpose: To build, test, and debug regular expressions before integrating them into source code. Use this tool whenever you are creating or modifying a regular expression.
- Syntax: ${strings/tool-prefix}REGEX/VALIDATE{ "regExString": "{SoRegEx}<raw_regex_pattern>{EoRegEx}", "flags": "<optional_flags>", "testCases": [ { "type": "validate", "input": "", "expected": <true_or_false> }, { "type": "extract", "input": "", "expected": "<extracted_string>", "group": 1 } ] }
- Rules and Usage:
- Core Principle: Isolate and Test the Smallest Part
- Think in Units: Treat RegEx validation like unit testing. When modifying a regular expression that is built from multiple parts in the code, you MUST identify and test only the specific component you are changing.
- DO NOT Reconstruct Complex Patterns: Avoid recreating large, multi-part regular expressions from the source code. This is error-prone and leads to overly complex tests. Your goal is to verify your specific change, not to re-implement the entire RegEx logic within the tool.
- Example: If the code is
final_regex = part_A + part_Band you only need to modifypart_A, your test should focus exclusively onpart_A.
- CRITICAL: RegEx Delimiters: To prevent parsing errors, the value of the
regExStringfield MUST be wrapped in the{SoRegEx...EoRegEx}delimiters. The tool is designed to handle this specific format.regExString(string): The Regular Expression pattern string to be tested, wrapped with the required delimiters. Do not escape any part of this, this should be the raw regex string to be evaluated.flags(string, optional): Flags for the RegEx engine (e.g., "i" for case-insensitive, "g" for global). Defaults to an empty string.testCases(array): An array of test case objects. Each object defines a single test and must contain:type: The type of test. Must be one of the following:validate: Returnstrueif the pattern is found,falseotherwise.extract: Extracts a string using capture groups.replace: Replaces matched text with a new string.findAll: Finds all non-overlapping matches.split: Splits the input string using the regex as a delimiter.
input: The string input for the test case.expected: The expected outcome. The data type depends on thetype(e.g., boolean forvalidate, string forextract, array forfindAll).group(number, optional): Fortype: 'extract', the capture group index. Defaults to0(the full match).replacement(string, optional): Fortype: 'replace', the string to replace matched patterns with.
- Return Value: The tool returns a JSON object with
isRegexValid, asummaryof test results, and atestResultsarray detailing the outcome of each individual test case.
- Core Principle: Isolate and Test the Smallest Part