made changes to the workflows

inference.py

@@ -47,11 +47,12 @@ SYSTEM_PROMPT = """\
 You are OrgOS Agent — an enterprise workflow automation agent.
 You operate across four SaaS applications: Jira, Zendesk, Salesforce, and Workday.
 
-Each turn you receive a JSON observation with:
-  - workflow_goal    : the task you must complete
-  - pending_steps    : remaining steps in the workflow
-  - app_states       : current state of each app
-  - schema_hints     : field renames in effect this episode (e.g. {"jira.priority": "severity"})
+Each turn you receive an observation with:
+  - workflow_goal    : the business objective you must achieve
+  - completed_steps  : step IDs already finished (e.g. ["A1", "A2"])
+  - app_states       : current state of each app — your primary source of truth
+  - schema_hints     : PARTIAL field renames in effect (e.g. {"jira.priority": "severity"})
+                       Not all drift is revealed — probe with get_* if a field is rejected.
   - active_rules     : current SLA / approval thresholds
   - message          : feedback from the last action
   - current_score    : your cumulative score (0.001–0.999)
@@ -74,18 +75,12 @@ Available apps and key operations:
 
 CRITICAL RULES:
 1. Read schema_hints FIRST — if "jira.priority" → "severity", use "severity" not "priority" in args.
-2. Complete ALL pending_steps in order.
-3. Do not repeat a successful action.
-4. If an operation fails, read the message carefully and adapt.
-5. Use list_* operations to discover record IDs when needed.
-6. Stop when pending_steps is empty or done=true.
-
-Example actions:
-  {"app": "zendesk", "operation": "acknowledge_ticket", "args": {"ticket_number": "ZD-001"}}
-  {"app": "jira", "operation": "create_issue", "args": {"title": "Bug fix for ACME-001", "linked_zendesk": "ZD-001"}}
-  {"app": "salesforce", "operation": "get_account", "args": {"account_id": "ACME-001"}}
-  {"app": "workday", "operation": "log_sla_event", "args": {"ticket_id": "ZD-001", "sla_met": true}}
-  {"app": "zendesk", "operation": "create_agent_profile", "args": {"employee_id": "EMP-NEW-001", "email": "jordan.riley@company.com", "name": "Jordan Riley"}}
+   If a field is rejected, use get_* or list_* to probe the current schema before retrying.
+2. Inspect app_states to determine what has been done and what still needs action.
+3. Use list_* and get_* operations to discover record IDs — never assume them.
+4. Do not repeat a successful action.
+5. If an operation fails, read the message and adapt your field names or args.
+6. Stop when completed_steps covers all workflow steps or done=true.
 """
 
 WORKFLOW_NAMES = {
@@ -139,18 +134,19 @@ def api_get(path: str) -> dict:
 # ------------------------------------------------------------------
 
 def obs_to_text(obs: dict) -> str:
+    completed = obs.get("completed_steps", [])
+    completed_str = ", ".join(completed) if completed else "none"
+
     lines = [
         f"current_score:  {obs['current_score']}",
         f"step_count:     {obs['step_count']}",
         f"workflow_id:    {obs['workflow_id']}",
+        f"completed_steps: [{completed_str}]",
         "",
         "=== WORKFLOW GOAL ===",
         obs["workflow_goal"],
         "",
-        "=== PENDING STEPS ===",
-        "\n".join(f"  - {s}" for s in obs["pending_steps"]) or "  (all steps complete!)",
-        "",
-        "=== SCHEMA HINTS (use these field names) ===",
+        "=== SCHEMA HINTS (partial — probe with get_* for unknown fields) ===",
         json.dumps(obs["schema_hints"], indent=2) if obs["schema_hints"] else "  (no drift — use canonical names)",
         "",
         "=== ACTIVE RULES ===",
@@ -159,7 +155,7 @@ def obs_to_text(obs: dict) -> str:
         "=== LAST MESSAGE ===",
         obs["message"],
         "",
-        "=== APP STATES ===",
+        "=== APP STATES (use these to determine what still needs to be done) ===",
     ]
     for app_name, view in obs.get("app_states", {}).items():
         lines.append(f"  [{app_name.upper()}]")

server/environment.py

@@ -220,8 +220,17 @@ class OrgOSEnvironment:
 
         # Workflow progress
         completed_steps = self._workflow.get_completed()
-        pending_steps   = self._workflow.get_pending()
         workflow_goal   = self._workflow.get_goal()
+        total_steps     = len(self._workflow._steps)
+        steps_done      = len(completed_steps)
+        # Expose only a progress count — agent must infer what's next from app states
+        if steps_done == total_steps:
+            pending_steps = []
+        else:
+            pending_steps = [
+                f"{steps_done}/{total_steps} steps completed — "
+                "inspect app states and schema_hints to determine your next action."
+            ]
 
         # Reward breakdown snapshot
         breakdown = RewardBreakdown(

server/workflow_engine.py

@@ -106,35 +106,25 @@ WORKFLOW_C_STEPS = [
 WORKFLOW_GOALS: Dict[str, str] = {
     "A": (
         "Workflow A — Customer Bug Fix: "
-        "A P1 bug has been reported via Zendesk (ticket ZD-001) by customer ACME-001. "
-        "Steps required: "
-        "(1) acknowledge Zendesk ticket ZD-001, "
-        "(2) create a new Jira issue linked to ZD-001, "
-        "(3) verify ACME-001's account status in Salesforce, "
-        "(4) assign the Jira issue (JIRA-001) to an engineer, "
-        "(5) log the SLA compliance event in Workday. "
-        "Use list operations if you need to discover record IDs."
+        "A P1 bug has been escalated through the support queue. "
+        "Investigate the open ticket, escalate it to the engineering tracker, "
+        "verify the affected customer's account health, ensure the issue has an assigned owner, "
+        "and record SLA compliance. "
+        "Use list operations to discover relevant record IDs before acting."
     ),
     "B": (
         "Workflow B — Employee Onboarding: "
-        "A new support engineer has joined the West team. "
-        "Employee ID: EMP-NEW-001, Name: Jordan Riley, department: support, territory: west. "
-        "Steps required: "
-        "(1) create an onboarding record in Workday for EMP-NEW-001, "
-        "(2) provision Jira access for EMP-NEW-001 via Workday, "
-        "(3) assign EMP-NEW-001 to the correct Salesforce territory (use any ACME-* account in the west region), "
-        "(4) create a Zendesk agent profile for EMP-NEW-001. "
-        "You have manager-level access."
+        "A new support engineer has joined the West team and needs to be fully set up. "
+        "Ensure their employment record exists, provision the appropriate tooling access, "
+        "assign them to the correct territory in your CRM, and create their support profile. "
+        "Query the relevant systems to identify the new employee and required accounts."
     ),
     "C": (
         "Workflow C — Churn Risk Alert: "
-        "Account ACME-003 (GlobalTech) is showing churn signals. "
-        "Steps required: "
-        "(1) flag ACME-003 as a churn risk in Salesforce, "
-        "(2) query recent support tickets for ACME-003 in Zendesk (use customer_id=ACME-003), "
-        "(3) list open Jira bugs related to ACME-003, "
-        "(4) assign an intervention owner to ACME-003 in Salesforce. "
-        "Focus account: ACME-003."
+        "An enterprise account is showing churn signals and requires immediate attention. "
+        "Flag the at-risk account, assess their recent support ticket volume and open bug history, "
+        "and assign an intervention owner. "
+        "Use discovery operations to identify the account before taking action."
     ),
 }