{% extends "base.html" %} {% block title %}Sraosha — {{ "New Contract" if mode == "create" else "Edit " + form.title }}{% endblock %} {% block head %} {% endblock %} {% block content %}
{{ err }}
Identity, steward, and contact metadata. Link the contract to a compliance team in the Governance step.
Unique identifier for the contract
Maps to info.owner (human or org). Not the compliance team—set that under Governance.
info.owner
Published in info.contact for this contract—not alert routing.
info.contact
Define the servers this contract connects to.
No servers yet. Click "Add Server" to define a data source.
Define tables and their columns. Use auto-discover or add them manually.
Select a server from Step 2 and discover tables automatically. If the server has a Connection linked, credentials are resolved automatically. Otherwise, enter credentials below.
No models yet. Add one manually or use Auto-Discover.
Configure how violations are handled.
Canonical link for compliance and rollups. Manage teams under Settings → Teams.
block = fail pipeline, warn = log and continue, log = silent
Map upstream table.column to local table.column for precise impact analysis.
Routes for violation alerts—separate from General Info contact fields.
Reusable Slack/email channels; optional YAML overrides on the right.
Merged into x-sraosha.notify for alert routing only—not info.contact.
x-sraosha.notify
You can edit the YAML directly above. When you submit, the YAML content takes precedence over form fields.