GTAF SDK

GTAF SDK is the adoption layer around the runtime core.

Governance models and runtime contracts are necessary, but they do not become useful at scale if every team has to rebuild loading, mapping, context shaping, and enforcement wiring on its own. The SDK exists to close exactly that gap.

Without an integration layer, governance often remains trapped between framework documentation and custom application code.

The SDK helps make runtime adoption repeatable. It standardizes the path into enforcement while making sure that the actual runtime semantics stay owned by the runtime core and do not get rewritten by helper abstractions.

That path matters because it defines how a real product or internal system enters a governed runtime instead of bypassing it.

The current public SDK implementation exposes the integration path concretely:

from gtaf_sdk.artifacts import load_runtime_inputs
from gtaf_runtime import enforce

drc, artifacts = load_runtime_inputs(
  drc_path="path/to/drc.json",
  artifacts_dir="path/to/artifacts",
)

result = enforce(
  drc,
  context,
  artifacts,
)

The important point is not the stack. The important point is that the integration layer remains thin enough to preserve the semantics of the runtime while still being strong enough to make adoption realistic.

GTAF SDK is especially relevant for teams that already know they need runtime governance, but need a path from architecture into working systems. Typical collaboration paths include:

• integrating governance artifacts into existing application and platform flows

• shaping action normalization, context models, and artifact management conventions

• defining a thin but robust contract between product code and runtime enforcement

• avoiding the common failure mode where helper layers accidentally reinterpret policy