TTD-105: Add Agentic, Skill, and Context Repository typedefs

[suseriAtlan]

Summary

• Adds Python SDK support for the new Agentic hierarchy introduced in atlanhq/models#1942 (TTD-105): Agentic supertype under Catalog, with Skill/SkillArtifact and ContextRepository/ContextArtifact concrete types, plus shared Artifact/Context bases.
• Creators on the 4 concrete types use NanoID-based qualifiedName patterns and auto-populate parent refs.
• Adds ContextLifecycleStatus enum and bumps FileType with yaml, sql (from models 1.1).

Type hierarchy

Catalog
└── Agentic
    ├── Artifact (extends Agentic + File)
    │   └── artifactVersion, fileType, filePath
    ├── Skill
    │   ├── skillVersion
    │   └── skillArtifacts → SkillArtifact
    ├── SkillArtifact (extends Artifact)
    │   └── skillSource → Skill
    └── Context
        ├── contextRepositoryQualifiedName
        ├── ContextRepository
        │   ├── contextRepositoryLifecycleStatus (enum)
        │   ├── contextRepositoryAgentInstructions (text)
        │   ├── contextRepositoryTargetConnectionQualifiedName
        │   └── contextArtifacts → ContextArtifact
        └── ContextArtifact (extends Context + Artifact)
            └── contextRepository → ContextRepository

qualifiedName patterns

Type	Pattern
Skill	default/skill/{nanoid}
SkillArtifact	{skill_qn}/artifact/{file_type}/{nanoid}
ContextRepository	default/context/{nanoid}
ContextArtifact	{repo_qn}/artifact/{file_type}/{nanoid}

End-to-end validation on ai-steward.atlan.com

All 4 concrete types round-trip on a real tenant (the models PR is deployed there):

Type	GUID
Skill	2976f4cb-c912-411e-bd36-aeead38e16e7
ContextRepository	9fac2866-5ed4-41ad-b055-0ce36bde70c4
SkillArtifact	4790ef7f-8946-4090-9213-538507fc0695
ContextArtifact	82dcde41-d8ff-446f-82f8-556d5097a7d2

Artifacts were created with FileType.TXT because ai-steward's file_type enum is still at 1.0; yaml/sql/md are rejected server-side until the enum bump is deployed. The Python enum here matches models 1.1 and is ready for that rollout.

Test plan

• Unit suite green: 3400 passed, 1 skipped (no regressions) after wiring
• isinstance, MRO, setter/getter round-trip, JSON camelCase serialization verified locally
• Creators produce expected qualifiedName patterns and populate parent refs (skill_source, context_repository)
• validate_required_fields rejects empty inputs
• Real-tenant create+read on ai-steward (GUIDs above)
• Retest with FileType.YAML / FileType.SQL once the 1.1 enum bump ships to tenants

Related

• Metastore: atlanhq/models#1942
• Bootstrap policies: atlanhq/atlas-metastore#6417
• Search indexing: atlanhq/atlan-search-app#63

🤖 Generated with Claude Code

[Aryamanz29]

Code Review — TTD-105: Agentic, Skill, and Context Repository typedefs

Overall

Clean, well-structured PR that adds the Agentic type hierarchy following existing pyatlan asset patterns closely. The type hierarchy (Catalog → Agentic → Skill/Context → SkillArtifact/ContextArtifact) is sound, creators use NanoID-based qualifiedName patterns correctly, and parent refs are auto-populated. The new ContextLifecycleStatus enum and FileType additions (yaml, sql) match models 1.1.

Positives

• Consistent patterns: All 7 new model files follow the exact same structure as existing assets (type_name validator, _convenience_properties, getter/setter pairs, Attributes inner class, bottom-of-file circular import resolution)
• Creator validation: validate_required_fields is used consistently on all 4 concrete types
• NanoID qualifiedNames: Patterns are clean and documented in the PR description
• Relationship wiring: skill_source / context_repository refs are auto-populated by creators via ref_by_qualified_name
• Forward refs: All update_forward_refs calls are wired in core/__init__.py

Suggestions

1. Docstrings: All 7 new classes have """Description""" as their docstring. Would be good to replace with actual descriptions matching the typedef definitions (e.g., """A skill represents a reusable capability within the Agentic hierarchy."""). Low priority but improves discoverability.

2. Artifact.file_assets type: In artifact.py:96, file_assets is typed as Optional[Asset] (singular). Should this be Optional[List[Asset]] based on the relation being named fileAssets (plural)? Same question for ContextArtifact.file_assets. Worth verifying against the metastore typedef.

3. Missing FILE_ASSETS field re-declaration in ContextArtifact: ContextArtifact extends Context (not Artifact), so it re-declares ARTIFACT_VERSION, FILE_TYPE, FILE_PATH, and FILE_ASSETS class fields. This is correct for the diamond inheritance pattern, but the file_assets attribute in ContextArtifact.Attributes shadows the one from Context.Attributes (which doesn't have it) and Artifact.Attributes (which does). Since ContextArtifact doesn't extend Artifact in the MRO, this is fine — just noting it's intentional.

4. ContextArtifact missing context_repository_qualified_name in Attributes.creator: The creator correctly sets context_repository_qualified_name on the attributes, which is good — this enables the Context.CONTEXT_REPOSITORY_QUALIFIED_NAME field to work for search. Looks complete.

5. Enum ordering in FileType: YAML and SQL are added before MD. The enum appears to be in alphabetical order up to HYPER, then YAML/SQL/MD break that pattern. Minor nit — could reorder to MD, SQL, YAML for consistency, but this doesn't affect functionality.

Tests

I've written 40 unit tests and integration tests covering:

• Unit (tests/unit/model/):
  • agentic_test.py — type hierarchy, MRO, isinstance checks
  • skill_test.py — creator validation, unique QN generation, getter/setter, immutability
  • skill_artifact_test.py — creator validation (3 params), QN pattern verification, file type variants (YAML/SQL), skill_source ref population
  • context_repository_test.py — creator validation, lifecycle status enum round-trip, all ContextLifecycleStatus values
  • context_artifact_test.py — creator validation (3 params), QN pattern, file type variants (YAML/SQL/MD), context_repository ref population, artifact_version/file_path setters
• Integration (tests/integration/agentic_test.py):
  • CRUD for all 4 concrete types (Skill, SkillArtifact, ContextRepository, ContextArtifact)
  • Retrieve by GUID with relationships
  • Certificate update on Skill
  • Delete + restore cycle for ContextArtifact

All 40 unit tests pass. Will push the test files to the branch.

Verdict

Approve — solid implementation following established patterns. The docstring and file_assets type suggestions are low priority and can be addressed in a follow-up.

[Aryamanz29]

LGTM - thanks @suseriAtlan! 🙌

I've updated the generator templates and added unit and integration tests (CRUD has been validated against https://eops1.atlan.com/context-studio). Please double-check the latest code changes - if it looks good, I can merge. Thanks!

[Aryamanz29]

 tests/integration/agentic_test.py ✓✓✓✓✓✓✓✓✓                                                                                                                                           100% ██████████

Results (21.39s):
       9 passed