mftsccs-node 0.0.78-dev → 0.0.80-dev

package/README.md

@@ -2,7 +2,7 @@
 
 **mftsccs-node** - Full Pack of Concept and Connection System
 
-A powerful TypeScript library for building knowledge graphs and managing complex relationships between concepts. CCS-JS provides a complete solution for creating, querying, and managing concepts and connections with support for transactions, runtime caching, and flexible schema querying.
+A powerful TypeScript library for building knowledge graphs and managing complex relationships between concepts. CCS-JS provides a complete solution for creating, querying, and managing concepts and connections with support for transactions, runtime caching, and flexible schema querying.
 
 [![npm version](https://img.shields.io/npm/v/mftsccs-node.svg)](https://www.npmjs.com/package/mftsccs-node)
 [![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
@@ -106,7 +106,7 @@ A **Composition** is a hierarchical structure of related concepts and connection
 
 ## ✨ Key Features
 
-- 🔄 **Runtime Caching**: In-memory compatibility store and backend synchronization helpers
+- 🔄 **Runtime Caching**: In-memory compatibility store and backend synchronization helpers
 - 🔐 **Security & Access Control**: Fine-grained permissions per concept/connection
 - 🌳 **Binary Tree Indexing**: O(log n) lookups by ID, character, and type
 - 📦 **Transactions**: ACID-like operations with rollback support
@@ -125,12 +125,22 @@ Initialize the CCS system before performing any operations:
 
 ```typescript
 import { init, updateAccessToken } from 'mftsccs-node';
+import { CCSConfig } from 'mftsccs-node';
+
+// Access control is disabled by default (all access allowed).
+// Enable it explicitly via CCSConfig when needed.
+const config = new CCSConfig({
+  accessToken: 'your-bearer-access-token',
+  enableAccessControl: true,
+  accessControlBaseUrl: 'https://access.example.com/api/access-control'
+});
 
-// Initialize with backend URLs and auth token
+// Initialize with backend URLs and config
 init(
   'https://api.freeschema.com',      // Base API URL
-  'https://ai.freeschema.com',       // AI service URL
-  'your-bearer-access-token'         // Authentication token
+  '',                                // Optional Node URL
+  'MyApp',                           // Application name
+  config
 );
 
 // Update token later if needed
@@ -139,8 +149,8 @@ updateAccessToken('new-access-token');
 
 **Important**:
 - Call `init()` once at application startup
-- `init()` returns a Promise; await it before making API calls that depend on auth or hydrated caches
-- `IdentifierFlags` are also updated for callers that poll readiness
+- `init()` returns a Promise; await it before making API calls that depend on auth or hydrated caches
+- `IdentifierFlags` are also updated for callers that poll readiness
 
 ```typescript
 import { IdentifierFlags } from 'mftsccs-node';
@@ -902,9 +912,9 @@ const retrieved = await GetComposition(composition.id);
 console.log(retrieved); // Full nested structure
 ```
 
-### Local Compatibility APIs
-
-Frontend-origin local/offline helpers are not exported by the Node package. Server consumers should use the backend-backed concept, connection, and composition APIs instead of local concept creation helpers.
+### Local Compatibility APIs
+
+Frontend-origin local/offline helpers are not exported by the Node package. Server consumers should use the backend-backed concept, connection, and composition APIs instead of local concept creation helpers.
 
 ### Bulk Operations
 
@@ -1009,7 +1019,7 @@ ccs-js/
 │   ├── Api/              # Backend API integration (45 files)
 │   ├── Services/         # Business logic layer (73+ files)
 │   ├── DataStructures/   # Core data models (70+ files)
-│   ├── Database/         # Node in-memory compatibility storage (4 files)
+│   ├── Database/         # Node in-memory compatibility storage (4 files)
 │   ├── Constants/        # Configuration (2 files)
 │   ├── Helpers/          # Utility functions (3 files)
 │   ├── Drawing/          # UI visualization (2 files)
@@ -1087,45 +1097,45 @@ const query = {
 const documents = await FreeschemaQueryApi(query, "token");
 ```
 
----
-
-## Local Package Testing
-
-You can call `SchemaQueryListener` from this repository without creating another project.
-
-1. Copy `scripts/.env.example` to `scripts/.env` and set `CCS_BASE_URL`, `CCS_ACCESS_TOKEN`, and optionally `CCS_SCHEMA_QUERY_FILE`.
-2. Edit `scripts/schema-query.example.json` or create another query JSON file.
-3. Run:
-
-```bash
-npm run schemaquery:test
-```
-
-To reuse an already-built `dist/bundle.js`, run:
-
-```bash
-npm run schemaquery:test:built -- --query scripts/schema-query.example.json
-```
-
-You can override values from the command line:
-
-```bash
-npm run schemaquery:test -- --query scripts/schema-query.example.json --base-url https://your-api-url.com --token your-token --type YourTypeName --format DATAID
-```
-
-The runner prints the full `SchemaQueryListener` result as JSON, including the top-level `count`.
-
-If the backend returns an error, inspect the raw API response:
-
-```bash
-npm run schemaquery:test:built -- --query scripts/schema-query.example.json --raw
-```
-
----
-
-## 🤝 Contributing
-
-Contributions are welcome! Please follow these steps:
+---
+
+## Local Package Testing
+
+You can call `SchemaQueryListener` from this repository without creating another project.
+
+1. Copy `scripts/.env.example` to `scripts/.env` and set `CCS_BASE_URL`, `CCS_ACCESS_TOKEN`, and optionally `CCS_SCHEMA_QUERY_FILE`.
+2. Edit `scripts/schema-query.example.json` or create another query JSON file.
+3. Run:
+
+```bash
+npm run schemaquery:test
+```
+
+To reuse an already-built `dist/bundle.js`, run:
+
+```bash
+npm run schemaquery:test:built -- --query scripts/schema-query.example.json
+```
+
+You can override values from the command line:
+
+```bash
+npm run schemaquery:test -- --query scripts/schema-query.example.json --base-url https://your-api-url.com --token your-token --type YourTypeName --format DATAID
+```
+
+The runner prints the full `SchemaQueryListener` result as JSON, including the top-level `count`.
+
+If the backend returns an error, inspect the raw API response:
+
+```bash
+npm run schemaquery:test:built -- --query scripts/schema-query.example.json --raw
+```
+
+---
+
+## 🤝 Contributing
+
+Contributions are welcome! Please follow these steps:
 
 1. Fork the repository
 2. Create a feature branch (`git checkout -b feature/amazing-feature`)