Develop Connector v2

1. Project Scope This project expands the existing Connector application with:  canonical data schemas and dictionaries;  capabilities and operational restrictions;  routing and fallback rules;  a production-ready internal connector runtime;  reliable synchronization, idempotency and retry mechanisms;  a lightweight canonical event intake and forwarding layer (Event Layer Lite);  n8n orchestration integration;  advanced flows and automations;  flow versioning, simulation, approvals and monitoring;  controlled AI-assisted mappings and flow drafting;  AI-assisted diagnosis, retry recommendations and anomaly detection. Important scope change: Event Layer Lite is new scope compared with the previous version of this project. Its estimated incremental effort is approximately 55–85 hours (about 7–11 working days for one developer), depending on the quality of the existing MVP, queue implementation and Matomo configuration. The revised percentages below apply to the revised total project price; the new work should not be absorbed into the previous price without adjustment. 2. Event Layer Lite — Purpose and Boundaries Event Layer Lite provides one reusable, controlled event channel so future Tour Guide, BookStack/knowledge, subscription, AI Help and Reward Score functions do not create five unrelated event implementations. The required architecture is: Tour Guide / BookStack / Subscriptions / AI Help / Reward Score ↓ Connector Event Layer Lite ↓ Basic Event Log + Queue ↓ Matomo Event Layer Lite must support:  one canonical event envelope and event-type naming convention;  user, organization/workspace, source application and source module identification;  secure event intake through API key, HMAC signature or another approved method;  schema validation and schema version identification;  unique event IDs, correlation IDs and idempotent processing;  basic event storage and operational statuses;  asynchronous queue-based forwarding to Matomo;  limited retry/replay using the project reliability layer;  API examples and reusable sender guidance for future source applications. This project does not include the full modification of the five source applications.  No Tour Guide plugin or application-specific implementation is required.  No BookStack plugin or deep BookStack customization is required.  No Rocket LMS subscription emitter is required in this project unless separately awarded.  No AI Help application modification is required.  No Reward Score application modification is required.  The developer must prove compatibility by sending representative sample events for all five categories through Postman, an equivalent API client or safe test fixtures. 6. Delivery Rules for Every Payment Milestone  Functional source code committed to the approved Git repository.  A separate branch, tag or release for the delivered payment milestone.  All required database migrations and safe test seeders.  Backup confirmation before deployment or significant database changes.  A precise changelog and list of known limitations.  Testing notes, including success and failure cases.  Installation or update documentation.  A functional walkthrough video.  Correction of milestone-blocking defects before payment release. Non-delivery: Screenshots, static HTML, duplicated submenu pages, placeholder CRUD, non-functional buttons, undocumented server-only changes or code that is not committed to the repository do not constitute milestone delivery. 7. Final Award and Scope Rules 1. Each payment milestone must receive a separate fixed price in the Freelancer.com proposal. 2. The percentages apply to the revised total project price only. 3. The developer must explicitly confirm that Event Layer Lite does not include modification of the five source applications. 4. Any application-specific event emitter, plugin or hook must be quoted as a separate future project or milestone. 5. Public SDK, Marketplace, independent Connector SaaS billing and a full replacement for n8n are outside this project. 6. A later task must not break an earlier accepted task. Developer-caused regressions must be corrected without being treated as new scope. 7. Final payment is released only after complete source-code handover, documentation, regression testing and final end-to-end demonstration.

Project ID: 40589868