Libraries Overview

Amadla's shared Go libraries provide common functionality used across all tools and plugins. They form a layered dependency hierarchy with LibraryUtils at the foundation.

Library Inventory

Library	Module	Purpose
LibraryUtils	github.com/AmadlaOrg/LibraryUtils	Foundation utilities: git, file, database, IPC, encryption
LibraryFramework	github.com/AmadlaOrg/LibraryFramework	CLI framework wrapper around Cobra
LibraryPluginFramework	github.com/AmadlaOrg/LibraryPluginFramework	Base plugin loading and IPC communication
LibraryDoormanFramework	github.com/AmadlaOrg/LibraryDoormanFramework	Doorman plugin specialization for secret sources
LibraryJudgeFramework	github.com/AmadlaOrg/LibraryJudgeFramework	Judge plugin specialization for compliance checks
LibraryEnjoinFramework	github.com/AmadlaOrg/LibraryEnjoinFramework	Enjoin plugin specialization for system state configuration

Dependency Graph

Build Order

Libraries must be built bottom-up due to replace directives:

1. LibraryUtils — No Amadla dependencies
2. LibraryFramework — Depends on LibraryUtils
3. LibraryPluginFramework — Depends on LibraryUtils
4. LibraryDoormanFramework — Depends on LibraryUtils
5. LibraryJudgeFramework — Depends on LibraryUtils, LibraryFramework
6. LibraryEnjoinFramework — Depends on LibraryUtils, LibraryFramework

Shared Patterns

All libraries follow these conventions:

• Interface-based design: Idiomatic Go naming (Git, File, Database)
• Struct implementations: Unexported structs (gitImpl, fileImpl)
• Constructors: New() functions returning interface types
• Mock generation: Mockery v2 configured in .mockery.yaml
• Testing: testify/assert + testify/mock (except hery which uses Ginkgo/Gomega)
• Local references: replace directives in go.mod for sibling directories