-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path__init__.py
More file actions
95 lines (84 loc) · 2.65 KB
/
__init__.py
File metadata and controls
95 lines (84 loc) · 2.65 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
# SPDX-License-Identifier: PROPRIETARY
# Copyright (c) 2025 Hardbound Contributors
#
# Hardbound - Enterprise AI Governance
# https://github.com/dp-web4/hardbound
"""
Hardbound: Enterprise AI Governance
Implements Web4 "team/society" structure for enterprise AI deployments:
- Team identity (root LCT)
- Member management
- Policy enforcement
- R6 workflow for auditable actions
- ATP resource tracking
- Reputation accrual
Uses enterprise terminology:
- Team (not society)
- Ledger (not blockchain)
- Admin (not law oracle)
- Member (not citizen)
DERIVATION & MODULARITY
=======================
Hardbound is a self-contained enterprise product. While it shares conceptual
ancestry with the open-source Web4 governance modules, it maintains its own
implementations for commercial deployment independence.
Derived modules:
- ledger.py: Enterprise ledger (derived from claude-code-plugin/governance/ledger.py)
- policy_entity.py: Enterprise PolicyEntity (derived from claude-code-plugin/governance/policy_entity.py)
The derivation relationship is documented for transparency but the codebases
are intentionally decoupled. Changes to the open-source modules do not
automatically flow to Hardbound, allowing:
- Independent versioning and release cycles
- Enterprise-specific features without open-source constraints
- Regulatory compliance requiring isolated code review
- Commercial licensing separate from MIT
For the open-source governance implementation, see:
- https://github.com/dp-web4/web4/tree/main/claude-code-plugin/governance
Each repo serves a different purpose:
- hardbound: Enterprise commercial product
- web4: Research and specification
- plugins/extensions: Public concept demonstrations
- 4-life: Public explainer and simulation
"""
from .team import Team, TeamConfig
from .member import Member, MemberRole
from .policy import Policy, PolicyRule
from .r6 import R6Request, R6Response, R6Status
from .activity_quality import ActivityWindow, ActivityTier
from .ledger import Ledger
from .policy_entity import (
PolicyEntity,
PolicyRegistry,
PolicyEvaluation,
PolicyConfig,
PolicyMatch,
PolicyDecision,
get_enterprise_preset,
)
__all__ = [
# Team/Society
'Team',
'TeamConfig',
'Member',
'MemberRole',
# Policy (legacy)
'Policy',
'PolicyRule',
# PolicyEntity (derived from open-source)
'PolicyEntity',
'PolicyRegistry',
'PolicyEvaluation',
'PolicyConfig',
'PolicyMatch',
'PolicyDecision',
'get_enterprise_preset',
# R6 workflow
'R6Request',
'R6Response',
'R6Status',
# Activity
'ActivityWindow',
'ActivityTier',
# Ledger (derived from open-source)
'Ledger',
]