jefflyt
- 37 skills
- 0 followers
- 1 week ago last updated
- ▌ Mandate 2 1 1 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.1.1 (Authorization and Access Control), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 1 2 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.1.2 (Secure Credential Management), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 1 3 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.1.3 (Segregation from Critical Systems), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 1 4 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.1.4 (Sensitive Data Handling in Training Data and System Prompts), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 1 5 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.1.5 (Just-in-Time (JIT) and Identity-Based MCP Authentication), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 2 2 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.2.2 (Prevention of Data and Model Poisoning), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 2 3 Runtime Evidence Intake Guide · jefflytCollect natural-language environment context and generate evidence collection guidance for Mandate 2.2.3 Secure Training and Fine-Tuning. Use when code is insufficient and operational proof is required for final compliance evaluation.
- ▌ Mandate 2 2 4 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.2.4 (Vector Database and Embedding Security), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 2 5 Runtime Evidence Intake Guide · jefflytCollect natural-language context and generate supporting evidence guidance for Mandate 2.2.5 Model Asset Protection. Use when evaluating operational controls such as encryption, key management, access governance, and exfiltration protections.
- ▌ Mandate 2 3 1 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.3.1 (Comprehensive Logging and Auditing), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 3 2 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.3.2 (Anomaly Detection), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 3 4 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.3.4 (Mitigation of Misinformation and Hallucination), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 3 7 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.3.7 (UI/UX Behavioural Safeguards and Trust Calibration), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 4 1 Runtime Evidence Intake Guide · jefflytGather natural-language context and generate runtime/process evidence collection guidance for Mandate 2.4.1 (Resource Consumption Limits), including concrete system command templates and artifact checklists for final compliance evaluation.
- ▌ Mandate 2 4 4 Runtime Evidence Intake Guide · jefflytCollect natural-language system context and generate supporting evidence guidance for Mandate 2.4.4 Secure Inter-Agent Communication, including mTLS, certificate lifecycle, and network policy proof.
- ▌ Mandate 2 4 6 Runtime Evidence Intake Guide · jefflytCollect natural-language context and generate evidence collection guidance for Mandate 2.4.6 Identity and Behavioural Attestation, covering agent identity lifecycle, signed manifests, watchdog telemetry, and runtime enforcement proof.
- ▌ Mandate 2 2 6 Code Evaluation · jefflytEvaluate compliance for Mandate 2.2.6 (MCP Registry and Tool Integrity Pinning) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 3 3 Code Evaluation · jefflytEvaluate compliance for Mandate 2.3.3 (Human Verification for Critical Actions) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 3 5 Code Evaluation · jefflytEvaluate compliance for Mandate 2.3.5 (Secure Input and Goal Management) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 3 6 Code Evaluation · jefflytEvaluate compliance for Mandate 2.3.6 (UI Transparency and Manifest Validation) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 4 2 Code Evaluation · jefflytEvaluate compliance for Mandate 2.4.2 (Secure Output Handling) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 4 3 Code Evaluation · jefflytEvaluate compliance for Mandate 2.4.3 (Prevention of Unintended Consequences) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 4 5 Code Evaluation · jefflytEvaluate compliance for Mandate 2.4.5 (Context Isolation and Memory TTL) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 4 7 Code Evaluation · jefflytEvaluate compliance for Mandate 2.4.7 (Restricted Execution and Function Banning) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.
- ▌ Mandate 2 1 1 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.1.1 (Authorization and Access Control). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 1 2 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.1.2 (Secure Credential Management). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 1 3 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.1.3 (Segregation from Critical Systems). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 1 4 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.1.4 (Sensitive Data Handling in Training Data and System Prompts). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 1 5 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.1.5 (Just-in-Time (JIT) and Identity-Based MCP Authentication). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 2 2 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.2.2 (Prevention of Data and Model Poisoning). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 2 4 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.2.4 (Vector Database and Embedding Security). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 3 1 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.3.1 (Comprehensive Logging and Auditing). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 3 2 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.3.2 (Anomaly Detection). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 3 4 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.3.4 (Mitigation of Misinformation and Hallucination). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 3 7 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.3.7 (UI/UX Behavioural Safeguards and Trust Calibration). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 4 1 Code Static Eval · jefflytEvaluate static code indicators for Mandate 2.4.1 (Resource Consumption Limits). Use when assessing partial code-evaluable controls and producing a confidence-scored static finding package before requesting runtime/process evidence.
- ▌ Mandate 2 2 1 Code Evaluation · jefflytEvaluate compliance for Mandate 2.2.1 (AI Supply Chain Security) using repository code and configuration analysis. Use when producing deterministic pass/fail findings with severity, mapped mitigated vulnerabilities, and file-level evidence.