Web Rules Management
PostQode's Web Rules Management system enables engineering leaders and DevOps administrators to define, version, and distribute coding guidelines, architectural constraints, and compliance rules across all team members automatically.
How Web Rules Work
- Central Authoring in Web Console:
- Navigate to Rules (
/rules) in the PostQode Web Console (app.postqode.ai). - Click Create Rule (
/rules/createRule). - Enter a descriptive Rule Name, category tags, and markdown-formatted instructions.
- Choose rule scope: Organization-wide (enforced across all teams) or Team-specific.
- Navigate to Rules (
- Rule Verification & Badges:
- Administrators can mark critical compliance rules as Verified.
- Verified rules display a distinctive shield badge and cannot be overridden by individual workspace settings.
- Automatic IDE Synchronization:
- Connected IDE clients (VS Code, IntelliJ, Eclipse, CLI) query
pq-serverupon task initialization and inject the latest active web rules into the system prompt context.
- Connected IDE clients (VS Code, IntelliJ, Eclipse, CLI) query
- Deterministic Enforcement:
- Agents strictly adhere to these rules during implementation planning, surgical code editing (
apply_patch), and API test suite creation.
- Agents strictly adhere to these rules during implementation planning, surgical code editing (
Example Enterprise Rule Definition
# Corporate Security & Architecture Standards
1. **Zero Secret Policy**: Never hardcode API keys, tokens, or credentials. Always resolve via environment variables (`process.env.*`) or secrets managers.
2. **Schema Validation**: All inbound HTTP endpoints must validate request parameters and payloads using Zod or Joi schemas.
3. **Deterministic Testing**: Every new business logic service must be accompanied by unit tests with at least 80% branch coverage.
4. **Immutable State**: State mutations in React/Zustand stores must use immutable updates or Immer produce blocks.