transilienceai/tpse-capability-packs

business-context-kb

Apply organisation-specific criticality, ownership, consequence, and terminology while preserving customer corrections. Use when a Business Context workflow needs the know stage.

原文の言語: 英語

collect-business-context

Collect organisation, application, owner, vendor, policy, architecture, and objective context from approved sources. Use when a Business Context workflow needs the collect stage.

原文の言語: 英語

model-business-portrait

Model applications, resources, data, exposure, owners, vendors, objectives, and evidence provenance. Use when a Business Context workflow needs the model stage.

原文の言語: 英語

normalize-business-entities

Normalize applications, people, vendors, documents, objectives, observations, inferences, and confirmations. Use when a Business Context workflow needs the normalize stage.

原文の言語: 英語

package-business-context

Package the durable business portrait, confidence, confirmed corrections, gaps, and questions. Use when a Business Context workflow needs the package stage.

原文の言語: 英語

resolve-knowledge-gaps

Ask only questions whose answers change a named scope, owner, obligation, priority, or decision. Use when a Business Context workflow needs the decide stage.

原文の言語: 英語

cloud-control-kb

Apply versioned hardening, compliance, exposure, and provider-control knowledge. Use when a Cloud Assurance workflow needs the know stage.

原文の言語: 英語

collect-cloud-inventory

Collect read-only cloud inventory with explicit account, region, service, and permission coverage. Use when a Cloud Assurance workflow needs the collect stage.

原文の言語: 英語

model-cloud-attack-surface

Model public entry points, trust, topology, identity reach, and crown-jewel paths. Use when a Cloud Assurance workflow needs the model stage.

原文の言語: 英語

normalize-cloud-findings

Normalize posture findings, raw configuration, duplicates, service errors, and scanner provenance. Use when a Cloud Assurance workflow needs the normalize stage.

原文の言語: 英語

package-cloud-assurance

Package posture, coverage, service errors, risk, deltas, and action with exact provenance. Use when a Cloud Assurance workflow needs the package stage.

原文の言語: 英語

prioritize-cloud-remediation

Rank fixes by business impact, attack-path reduction, effort, confidence, and verification. Use when a Cloud Assurance workflow needs the decide stage.

原文の言語: 英語

code-rule-kb

Apply versioned SAST, secret, license, and vulnerability-advisory knowledge without inventing a passing result when a lookup fails. Use when a Code Assurance workflow needs the know stage.

原文の言語: 英語

collect-code-evidence

Collect commit-scoped files, manifests, settings, scanner diagnostics, and coverage gaps. Use when a Code Assurance workflow needs the collect stage.

原文の言語: 英語

model-code-risk

Build dataflow, dependency, trust-boundary, and source-to-sink models with language-tier confidence. Use when a Code Assurance workflow needs the model stage.

原文の言語: 英語

normalize-code-inventory

Normalize languages, files, dependencies, findings, confidence, and stable fingerprints. Use when a Code Assurance workflow needs the normalize stage.

原文の言語: 英語

package-code-assurance

Package SAST, SCA, SBOM, dataflow, risk, coverage, and remediation into traceable outcomes. Use when a Code Assurance workflow needs the package stage.

原文の言語: 英語

prioritize-code-remediation

Rank SAST, SCA, secret, and license work by exploitability, business consequence, effort, and verification path. Use when a Code Assurance workflow needs the decide stage.

原文の言語: 英語

assess-readiness-gaps

Determine met, open, unknown, partial, and not-applicable states; explain what evidence establishes and what remains. Use when a Compliance Assurance workflow needs the decide stage.

原文の言語: 英語

collect-control-evidence

Collect reusable evidence and record missing, denied, failed, unavailable, stale, and looked-found-none states separately. Use when a Compliance Assurance workflow needs the collect stage.

原文の言語: 英語

framework-control-kb

Maintain versioned framework requirements, unified controls, mappings, evidence expectations, and applicability logic. Use when a Compliance Assurance workflow needs the know stage.

原文の言語: 英語

model-control-evidence

Build scope-to-control-to-assertion-to-evidence lineage and preserve independent-engine disagreement. Use when a Compliance Assurance workflow needs the model stage.

原文の言語: 英語

normalize-control-signals

Normalize evidence, scanner, business, code, cloud, data, and identity signals into attributable control inputs. Use when a Compliance Assurance workflow needs the normalize stage.

原文の言語: 英語

package-assurance-report

Package readiness, why, risk, recommendations, conclusion, scope, provenance, decisions, work, and sign-off. Use when a Compliance Assurance workflow needs the package stage.

原文の言語: 英語

collect-cloud-costs

Collect billing usage, prices, commitments, credits, tags, accounts, services, and source coverage read-only. Use when a Cost Assurance workflow needs the collect stage.

原文の言語: 英語

cost-policy-kb

Apply versioned commitment, anomaly, waste, allocation, and unit-economics knowledge. Use when a Cost Assurance workflow needs the know stage.

原文の言語: 英語

model-cost-drivers

Model trends, anomalies, commitments, usage drivers, business changes, and allocation uncertainty. Use when a Cost Assurance workflow needs the model stage.

原文の言語: 英語

normalize-cost-allocation

Normalize spend by provider, account, service, owner, application, environment, and allocation confidence. Use when a Cost Assurance workflow needs the normalize stage.

原文の言語: 英語

package-cost-outcome

Package the why, risk, recommendation, conclusion, allocation gaps, and fresh-run savings verification. Use when a Cost Assurance workflow needs the package stage.

原文の言語: 英語

prioritize-cost-actions

Rank recommendations by savings, confidence, business risk, reversibility, effort, and required decision. Use when a Cost Assurance workflow needs the decide stage.

原文の言語: 英語

assess-data-risk

Assess exposure, obligation, scope, confidence, unknowns, and the safest next evidence or remediation action. Use when a Data Security workflow needs the decide stage.

原文の言語: 英語

collect-data-metadata

Enumerate source metadata first and distinguish connected, denied, failed, and looked-found-none states. Use when a Data Security workflow needs the collect stage.

原文の言語: 英語

data-classification-kb

Apply versioned sensitive-data, credential, privacy, and regulatory detector knowledge with redacted evidence. Use when a Data Security workflow needs the know stage.

原文の言語: 英語

model-data-flows

Model classified data movement, identity, storage, applications, processors, and trust boundaries. Use when a Data Security workflow needs the model stage.

原文の言語: 英語

normalize-data-catalog

Normalize sources, objects, tables, fields, owners, content identities, and collection coverage. Use when a Data Security workflow needs the normalize stage.

原文の言語: 英語

package-data-assurance

Package catalog, classifications, flows, risks, read audit, gaps, and recommendations. Use when a Data Security workflow needs the package stage.

原文の言語: 英語

channel-policy-kb

Apply audience, channel, content, confidentiality, escalation, and attribution policy. Use when a Delivery workflow needs the know stage.

原文の言語: 英語

collect-delivery-state

Collect assignment, outbox, destination, receipt, retry, and external-status state with provenance. Use when a Delivery workflow needs the collect stage.

原文の言語: 英語

decide-delivery-path

Choose the safest useful destination, content depth, timing, fallback, and required approval. Use when a Delivery workflow needs the decide stage.

原文の言語: 英語

model-work-routing

Model accountable owners, destinations, dependencies, retries, blockers, and scheduled delivery. Use when a Delivery workflow needs the model stage.

原文の言語: 英語