thinkwork-cli 0.12.12 → 0.12.15

package/dist/plugins/company-brain/terraform/cognee/README.md

@@ -0,0 +1,263 @@
+# Cognee Module (internal Company Brain substrate)
+
+Cognee is the internal implementation substrate behind tenant-scoped Company
+Brain instances. Company Brain is the customer-facing product name; Cognee
+should appear only in operator evidence, Terraform, logs, and implementation
+docs. The module is **not** the memory engine, does not replace Hindsight, and
+does not ingest or migrate Wiki/Brain content during Terraform apply.
+
+## What it creates
+
+When the parent module enables Cognee, this module provisions:
+
+- ECS Fargate cluster, task definition, and service for the Cognee API on port 8000.
+  Legacy stage-wide deployments use the Brain-named cluster
+  `thinkwork-{stage}-brain-cluster`; Cognee remains the service, task family,
+  container, database, log, and implementation key.
+- Internal Application Load Balancer. There is no internet-facing endpoint mode
+  in phase 1.
+- Security groups for ALB to Cognee, Cognee to Aurora, and Cognee to EFS.
+- EFS encrypted storage mounted at `/app/cognee-storage`, with Cognee
+  `DATA_ROOT_DIRECTORY` and `SYSTEM_ROOT_DIRECTORY` rooted below it.
+- CloudWatch log group `/thinkwork/{stage}/brain/{brain_instance_key}/cognee`
+  for tenant-scoped Brain instances, or the legacy `/thinkwork/{stage}/cognee`
+  path when no Brain identity is provided.
+- Task/execution IAM roles, including explicit Bedrock invoke permissions and
+  Secrets Manager access for ECS secret injection.
+- Optional scoped IAM access to canonical Brain S3 artifact prefixes and a
+  Neptune Analytics graph ARN.
+
+Tenant-scoped instances derive all AWS resource names from
+`brain_instance_key` (or `brain_tenant_id` when the key is empty). This prevents
+two tenant Brain instances in the same stage from targeting the same ECS, ALB,
+EFS, secret, or log group names. Leaving both values empty preserves the legacy
+stage-wide Cognee resource names for existing deployments except the
+operator-facing ECS cluster name, which is Brain-named.
+
+## Enablement checklist
+
+Cognee is disabled by default at the composite module, greenfield example,
+CLI-generated root, enterprise deploy template, and CI workflow surfaces. Existing
+deployments should not expect Cognee resources until `enable_cognee = true` is
+set explicitly.
+
+Before enabling it, prepare these operator-owned inputs:
+
+- `cognee_image_uri` pinned to an immutable `@sha256:` digest.
+- `cognee_db_password_secret_arn` for the dedicated `cognee_db_username`
+  database user. Do not reuse the shared Thinkwork admin database secret.
+- `cognee_bedrock_model_resource_arns` for the selected Bedrock LLM and
+  embedding models, or non-Bedrock provider secret ARNs when using external
+  providers.
+- `cognee_allowed_internal_cidr_blocks` or
+  `cognee_allowed_internal_security_group_ids` for the callers allowed to reach
+  the internal ALB.
+- `cognee_backend_mode`, `cognee_desired_count`, and graph/vector configuration.
+  Keep dogfood mode at one task; use remote stores before scaling out.
+- `cognee_brain_storage_tier`:
+  - `default` uses Cognee Postgres metadata plus local LanceDB/Kuzu-style stores
+    on the task storage substrate and must stay single-task.
+  - `production` uses Cognee-supported Neptune Analytics graph/vector providers.
+    It requires `cognee_neptune_graph_id` and `cognee_neptune_endpoint`; pass
+    `cognee_neptune_graph_arn` when the task needs graph query IAM.
+- Canonical Brain S3 roots (`cognee_brain_s3_artifact_root`,
+  `cognee_brain_s3_manifest_root`, and
+  `cognee_brain_s3_vault_projection_root`) for evidence. When the runtime must
+  read/write artifacts, also pass `cognee_brain_artifacts_bucket_arn` and the
+  tenant prefixes in `cognee_brain_artifacts_prefixes`.
+
+After apply, inspect these outputs instead of reconstructing resource names:
+
+- `cognee_enabled`
+- `cognee_endpoint`
+- `cognee_log_group_name`
+- `cognee_backend_mode`
+- `cognee_cluster_arn`
+- `cognee_service_name`
+- `cognee_security_group_id`
+- `cognee_storage_file_system_id`
+- `cognee_brain_instance_key`
+- `cognee_brain_tenant_id`
+- `cognee_brain_storage_tier`
+- `cognee_graph_database_provider`
+- `cognee_vector_db_provider`
+- `cognee_embedding_model`
+- `cognee_embedding_dimensions`
+- `cognee_s3_artifact_root`
+- `cognee_s3_manifest_root`
+- `cognee_s3_vault_projection_root`
+- `cognee_neptune_graph_id`
+- `cognee_neptune_endpoint`
+- `cognee_private_substrate_mode`
+- `cognee_production_posture`
+
+Terraform proves that the infrastructure graph is syntactically valid and that
+ECS reached steady state when `wait_for_steady_state = true`. It does not prove
+that Cognee can serve ontology work, that provider credentials are populated, or
+that any Wiki/Brain content has migrated.
+
+## Phase-1 network contract
+
+The ALB is internal-only (`internal = true`). ECS tasks run in the existing
+public subnets with `assign_public_ip = true` so they can reach Bedrock, ECR,
+Secrets Manager, CloudWatch Logs, and optional external providers without NAT
+gateway or VPC endpoint work in this pass.
+
+The Cognee task security group accepts inbound traffic only from the internal
+ALB. The ALB accepts inbound traffic only from
+`allowed_internal_cidr_blocks`/`allowed_internal_security_group_ids`.
+All-network CIDRs such as `0.0.0.0/0` and `::/0` are rejected.
+
+ThinkWork owns tenant/user authorization at the GraphQL and worker boundaries.
+Because this module exposes Cognee only on a private internal ALB, the default
+posture keeps Cognee-native request authentication and backend access control
+disabled (`REQUIRE_AUTHENTICATION=false`,
+`ENABLE_BACKEND_ACCESS_CONTROL=false`) for current worker compatibility. The
+posture is now explicit: `private_substrate_mode` must remain `true`, while
+`require_authentication`, `enable_backend_access_control`, and
+`cors_allowed_origins` map directly to Cognee security variables for future
+hardening. Do not reuse this module shape for an internet-reachable endpoint.
+
+## Backend modes
+
+| Brain tier   | Backend mode | Graph/vector stores                         | Scale contract                         |
+| ------------ | ------------ | ------------------------------------------- | -------------------------------------- |
+| `default`    | `dogfood`    | local Kuzu/LanceDB-style stores on task EFS | `desired_count = 1`; not HA            |
+| `production` | `remote`     | Neptune Analytics providers                 | Requires Neptune graph id and endpoint |
+
+Dogfood mode is deliberately single-task because Cognee's local Kuzu/LanceDB
+style stores are not suitable for concurrent writers. Use remote stores before
+raising `desired_count` above 1. Production tier intentionally rejects direct
+OpenSearch/OpenSearch Serverless/AOSS vector storage; Neptune Analytics is the
+supported production graph/vector path for this contract.
+
+## Deployment-runner contract
+
+The Step Functions deployment runner invokes the managed-app adapter with a
+payload shaped like:
+
+```json
+{
+  "phase": "plan",
+  "appKey": "cognee",
+  "tenantId": "tenant-id",
+  "jobId": "deployment-job-id",
+  "desiredConfig": {
+    "brainTenantId": "tenant-id",
+    "brainInstanceKey": "tenant-<stable-hash>",
+    "brainStorageTier": "default",
+    "privateSubstrateMode": true
+  }
+}
+```
+
+Net-new Company Brain installs seed that tenant identity in the plugin
+infrastructure handler. Existing/adopted rows preserve their stored
+`desired_config` so no-change adoption evidence remains meaningful. The runner
+maps `desiredConfig` to `cognee_*` Terraform variables, including tier defaults:
+`default` becomes dogfood + LanceDB/Kuzu, and `production` becomes remote +
+Neptune Analytics. Terraform state is still owned by the normal deployment
+control-plane job for the stage; the tenant-scoped resource names prevent
+instances from colliding inside that state.
+
+## Secret handling
+
+Sensitive values enter the ECS task through the `secrets` block, not the normal
+environment list:
+
+- `DB_PASSWORD` is read from `db_password_secret_arn` JSON key `password`.
+  Use a dedicated least-privilege Cognee database user. Do not pass the shared
+  Aurora admin/master credential.
+- Optional non-Bedrock `LLM_API_KEY` and `EMBEDDING_API_KEY` values come from
+  their matching secret ARN inputs.
+- Optional remote vector/graph credentials use `VECTOR_DB_KEY` and
+  `GRAPH_DATABASE_PASSWORD` secret ARN inputs.
+
+Bedrock is the default LLM and embedding provider path, so no provider API key is
+needed by default. Callers must still pass the specific
+`bedrock_model_resource_arns` Cognee may invoke. If a non-Bedrock provider cannot
+consume secrets through ECS secret injection, do not enable that provider mode
+until a wrapper/entrypoint is added.
+
+The module accepts pre-existing secret ARNs by default. For deployments that
+want Terraform to create the secret containers, set
+`create_secret_placeholders = true`. Terraform then creates only the missing
+secret containers required by the selected configuration:
+
+- `thinkwork/{stage}/cognee/db-credentials`
+- `thinkwork/{stage}/cognee/llm-api-key`
+- `thinkwork/{stage}/cognee/embedding-api-key`
+- `thinkwork/{stage}/cognee/vector-db-key`
+- `thinkwork/{stage}/cognee/graph-database-password`
+
+Tenant-scoped Brain instances use the equivalent
+`thinkwork/{stage}/brain/{brain_instance_key}/...` paths.
+
+Secret versions are seeded with `PLACEHOLDER_SET_VIA_CLI` and use
+`lifecycle.ignore_changes = [secret_string]`. Operators populate or rotate the
+real values with Secrets Manager after apply, and later Terraform applies do not
+clobber those values. Outputs expose only the selected secret ARNs.
+
+`vector_db_url` and `graph_database_url` must not embed credentials in userinfo
+or query parameters. Put remote-store credentials in the matching secret ARN
+inputs.
+
+## Image pinning
+
+`image_uri` is required and must be pinned to an immutable `@sha256:` digest.
+Mutable public tags such as `cognee/cognee:main` are intentionally rejected
+because the task can access customer knowledge stores, secrets, and Bedrock.
+
+## Smoke expectations
+
+Terraform validation proves syntax and dependencies, not runtime readiness.
+After enabling Cognee in a stage, operators should verify:
+
+- `cognee_enabled` is `true`, `cognee_backend_mode` matches the intended mode,
+  and `cognee_endpoint` is an internal ALB URL.
+- `cognee_cluster_arn`, GraphQL `deploymentStatus.cogneeClusterArn`, the Cognee
+  managed application `clusterArn`, and the health-check target all normalize to
+  the Brain cluster name for legacy stage-wide deployments.
+- `cognee_brain_storage_tier`, graph/vector providers, S3 roots, EFS id, and
+  Neptune graph evidence match the intended tenant Brain instance.
+- The internal ALB health check is healthy and the health endpoint is reachable
+  from the intended caller network or security group.
+- Terraform waited for ECS steady state, or operators manually confirmed the
+  service is stable if `wait_for_steady_state = false` was used.
+- `cognee_log_group_name` points to logs where Cognee boots without provider,
+  database, graph, vector, or filesystem errors.
+- Cognee reports the configured LLM, embedding, graph, and vector providers.
+- Cognee can call the selected LLM/embedding provider.
+- Cognee can reach the configured relational, vector, and graph stores.
+
+Committed verification evidence must redact account IDs, raw secret ARNs, full
+resource IDs, and environment values. Keep raw AWS/GraphQL evidence in the
+restricted CI, S3, or operator record, and commit only the sanitized summary.
+
+If startup fails, start with the ECS service events and the Cognee CloudWatch log
+group. Provider failures usually indicate missing Bedrock ARNs, missing
+Secrets Manager values, or unsupported provider/credential plumbing. Database,
+graph, and vector failures usually indicate connectivity, URL, secret, or
+backend-mode mismatches.
+
+## Rollback
+
+To disable the substrate, set `enable_cognee = false` and apply through the
+normal deploy pipeline. That removes the ECS service, internal ALB, security
+groups, and Terraform-owned storage/secrets for the module. It does not roll back
+or rewrite approved ontology definitions, Brain pages, Wiki content, or agent
+context. Those product migrations are owned by later application-level work.
+
+For a failed rollout where data should be preserved, scale or disable callers
+first, snapshot/export EFS or remote graph/vector stores as appropriate, and then
+apply the Terraform change. Do not manually mutate production resources outside
+the normal incident/deploy process.
+
+## Cleanup
+
+EFS stores persistent Cognee data/system files. Destroying the module may delete
+that storage if Terraform owns it. Remote graph/vector stores may retain data
+outside Terraform entirely. Treat production data cleanup as an operator
+decision: snapshot or export before destructive changes, and document whether the
+data belongs to the Terraform-owned EFS volume, an operator-managed remote store,
+or both.