Business Central Configuration and Policy Engine

This dedicated server infrastructure furnishes codified development mandates and project context specifically tailored for Business Central undertakings, featuring deep integration capabilities with the Cursor IDE environment.

Core Capabilities

• Static Policy Sets: Immutable development guidelines persisted within dedicated JSON artifact files, consumable directly by the Cursor editor.
• Render Deployment Facilitation: Streamlined mechanism for provisioning the service onto the Render.com platform.
• Database Independence: Operational continuity maintained even when direct database connectivity is absent.
• Collaborative Enforcement: Policies are automatically propagated and enforced across all engaged personnel within the shared repository space.

Initial Setup Guide

For Development Team Members

To integrate the established Business Central governance standards into your active workspace:

1. Obtain a local copy of this repository, or manually transfer the following critical files into your root project directory:
2. bc-rules.json

3. .cursor-context

4. The Cursor IDE will autonomously detect and instantiate these established parameters upon file access within the project boundary.

For System Administrators / Governance Owners

To revise or oversee the established rule set:

1. Direct modification of bc-rules.json enables immediate alteration of static policies.
2. Alternatively, leverage the backend MongoDB instance for dynamic, centralized storage and management of evolving policies.
3. Execute node scripts/generateRules.js to synchronize any database-held dynamic rules back into the static deployment artifact.

Operational Deployment

Utilizing Render (Recommended Pathway)

1. Execute the utility script ./scripts/deployRender.sh to finalize preparatory steps for deployment.
2. Commit and push changes to the designated GitHub repository.
3. Establish the official connection link between the repository and the Render.com hosting environment.
4. Configure essential environment variables within the Render administrative console:
5. NODE_ENV: Set to production
6. MCP_SERVER_PORT: Designate as 10000 (or preferred alternative)
7. MONGODB_URI: Supply the connection string for the backing MongoDB data store (this is optional if only static rules are utilized).

Service Access Points (Endpoints)

• /cursorrules: Retrieves the currently active, consolidated policy manifest in JSON format.
• /health: Reports the operational status and availability of the configuration service.

Manifest Schema Example

Policies adhere to the following structural blueprint:

{
  "version": "1.0",
  "rules": [
    "Adherence to corporate naming conventions for all compiled artifacts",
    "Mandatory inclusion of robust exception handling within every defined procedure"
  ],
  "context": {
    "businessDomain": "Business Central ERP",
    "preferredPatterns": ["Data Access Layer pattern", "Adherence to all SOLID principles"]
  }
}