docs: Add documentation for extension and proposal traits

Author: whoabuddy

docs/dao/traits/extension.md

@@ -0,0 +1,57 @@
+# Extension Trait
+
+The extension trait defines the base interface that all DAO extensions must implement.
+
+## Interface
+
+```clarity
+(define-trait extension (
+  (callback (principal (buff 34)) (response bool uint))
+))
+```
+
+## Functions
+
+### callback
+Standard extension callback support.
+- Parameters:
+  - `sender`: Calling principal
+  - `memo`: Optional callback data (34 bytes)
+- Returns: Success/failure response
+
+## Implementation Requirements
+
+1. Handle callbacks from DAO and other extensions
+2. Process callback memos appropriately
+3. Return meaningful success/failure responses
+4. Implement authorization checks
+5. Log callback events consistently
+
+## Usage Pattern
+
+Extensions should implement callback to:
+1. Receive notifications from other extensions
+2. Process cross-extension requests
+3. Handle DAO-initiated actions
+4. Support extension-specific callbacks
+
+Example implementation:
+```clarity
+(define-public (callback (sender principal) (memo (buff 34)))
+  (begin
+    ;; Verify sender is DAO or extension
+    (try! (is-dao-or-extension))
+    
+    ;; Process callback
+    (print {
+      notification: "callback",
+      payload: {
+        sender: sender,
+        memo: memo
+      }
+    })
+    
+    (ok true)
+  )
+)
+```

docs/dao/traits/proposal.md

@@ -0,0 +1,59 @@
+# Proposal Trait
+
+The proposal trait defines the interface that all DAO proposals must implement.
+
+## Interface
+
+```clarity
+(define-trait proposal (
+  (execute (principal) (response bool uint))
+))
+```
+
+## Functions
+
+### execute
+Executes the proposal's changes.
+- Parameters:
+  - `sender`: Principal initiating execution
+- Returns: Success/failure response
+
+## Implementation Requirements
+
+1. Verify execution authorization
+2. Make atomic state changes
+3. Return meaningful success/failure
+4. Log execution events
+5. Handle errors gracefully
+
+## Usage Pattern
+
+Proposals should:
+1. Implement authorization checks
+2. Make targeted state changes
+3. Emit comprehensive logs
+4. Return clear status
+
+Example implementation:
+```clarity
+(define-public (execute (sender principal))
+  (begin
+    ;; Verify sender
+    (asserts! (is-eq sender .aibtcdev-dao) ERR_UNAUTHORIZED)
+    
+    ;; Make changes
+    (try! (contract-call? .aibtcdev-dao set-something new-value))
+    
+    ;; Log execution
+    (print {
+      notification: "proposal-executed",
+      payload: {
+        sender: sender,
+        changes: "..."
+      }
+    })
+    
+    (ok true)
+  )
+)
+```