house-lights 1.2.1 → 1.3.0

package/skills/cast-list/examples/agents/bodega-pedidos/topics/ConsultarPoliticasPedidos Copy.topic.mcs.yml

@@ -0,0 +1,56 @@
+mcs.metadata:
+  componentName: Consultar Políticas de Pedidos Copy
+  description: "Responde dúvidas sobre pedidos com base nas políticas publicadas no SharePoint."
+kind: AdaptiveDialog
+inputs:
+  - kind: AutomaticTaskInput
+    propertyName: PerguntaCliente
+    description: "A pergunta do cliente sobre pedidos, status, cancelamento ou pagamento."
+    shouldPromptUser: true
+
+modelDescription: "Responde perguntas sobre status de pedido, prazos de processamento, cancelamento antes do envio e formas de pagamento da Bodega Azul."
+beginDialog:
+  kind: OnRecognizedIntent
+  id: main
+  intent: {}
+  actions:
+    - kind: CreateSearchQuery
+      id: createSearchQuery_LQyhy8
+      userInput: =Topic.PerguntaCliente
+      result: Topic.SearchQuery
+
+    - kind: SearchAndSummarizeContent
+      id: searchContent_O7ySob
+      autoSend: false
+      variable: Topic.SearchResult
+      userInput: =Topic.SearchQuery.SearchQuery
+      fileSearchDataSource:
+        searchFilesMode:
+          kind: DoNotSearchFiles
+
+      knowledgeSources:
+        kind: SearchSpecificKnowledgeSources
+        knowledgeSources:
+          - cr7b2_bodegaPedidos.knowledge.PoliticasPedidos
+
+      applyModelKnowledgeSetting: false
+      responseCaptureType: FullResponse
+
+    - kind: SetVariable
+      id: setVariable_f4lXT8
+      variable: Topic.Resposta
+      value: =Topic.SearchResult.Text.Content
+
+inputType:
+  properties:
+    PerguntaCliente:
+      displayName: PerguntaCliente
+      description: "A pergunta do cliente sobre pedidos, status, cancelamento ou pagamento."
+      type: String
+
+outputType:
+  properties:
+    Resposta:
+      displayName: Resposta
+      description: Resposta fundamentada na base de conhecimento do agente.
+      type: String

package/skills/cast-list/examples/profile.cast.yaml

@@ -9,6 +9,34 @@ min_agents: 3      # …with at least 3 agents in that role
 rules:
   - { id: escala, role: specialist, has: "trigger:OnEscalate", says: "Todo especialista escala para humano" }
   - { id: kpi, role: specialist, has: "declared:kpi", says: "Todo especialista tem KPI" }
+  # what the text says against how the agent is set up
+  - { id: knowledge-only, when: "text:knowledge-only", not: "setting:model-knowledge=on",
+      says: "Quem pede só o conhecimento tem o conhecimento geral desligado" }
+
+# what to look for in the text (JavaScript regular expressions; case does not matter)
+markers:
+  - { id: size, name: Tamanho da resposta, in: instructions,
+      pattern: '(no máximo|at most|up to)\s*(\d+)\s*(bullets?|frases?|sentences?)', value: "$2 $3" }
+  - { id: no-emoji, name: Sem emojis, pattern: '(sem|não use|no)\s+emojis?' }
+  - { id: knowledge-only, name: Só o conhecimento, pattern: '(somente|apenas|only)[^.]{0,40}(conhecimento|knowledge)' }
+
+# the block the team pastes in every specialist
+blocks:
+  - id: links
+    name: Formatação de links
+    text: |
+      Links:
+      - Formate links assim: [título](url), nunca a URL crua.
+      - Um link de ação vai no topo; o link da base de ajuda vai no fim.
+      - Nunca escreva as palavras «clique aqui».
+      - No máximo 3 links por resposta.
+
+# the kinds of specialist: one may be of two types; patterns are also found within each type
+types:
+  - { id: transaction, name: transação, when: { any: ["flow:*"] } }
+  - { id: guidance, name: orientação, when: { all: ["text:link-domain:*", "node:SearchAndSummarizeContent"] } }
+  - { id: triage, name: triagem, when: { any: ["trigger:OnSelectIntent"] } }
+
 focus_areas:
   - { id: confiabilidade, name: Confiabilidade, facts: ["trigger:OnError", "node:LogCustomTelemetryEvent", "ms:rai-error-handling"] }
 ignore: ["trigger:OnConversationStart"]

package/skills/cast-list/references/format.md

@@ -11,7 +11,12 @@ format: cast-list/cast-v1
 name: Customer service agents
 agents:                      # the roles of the last run (an agent the profile does not name keeps its role here)
   - { id: main-orchestrator, role: orchestrator }
-  - { id: returns, role: specialist }
+  - { id: returns, role: specialist, types: [ transaction ] }   # types a person gives win over the profile's
+blocks:                      # the blocks of text of the last run, so a block keeps its id across small edits
+  - id: links
+    text: |
+      Links:
+      - Format links as [title](url), never the bare URL.
 declared:                    # what a document or a person says — always with its source
   - { agent: returns, key: kpi, value: "time to answer < 2 min", source: "backlog, epic 12" }
   - { agent: shipping, key: "trigger:OnEscalate", value: "yes", source: "handoff, section 4" }
@@ -19,11 +24,13 @@ decisions:                   # what the team decided about a pattern
   - { key: "trigger:OnEscalate", status: accepted, scope: platform, why: "Nobody is left without a person" }
 ```
 
+- **blocks** and the roles are written by the run; **types** are written only by a person (the ones the profile works
+  out are not kept, so a change in the profile still holds).
 - **declared**: `key` is either something only people know (`kpi`, `owner`, any word: it becomes `declared:<key>`) or a
   fact key (`trigger:OnEscalate`, `references/keys.md`) when a document claims the agent does it. `value` `no` / `não` /
   `false` claims it does **not**. A claim never changes what the YAML shows: when they disagree, it is a conflict.
-- **decisions**: `status` is `accepted` or `rejected`; `scope` is `platform` (every agent), `specialist` or
-  `orchestrator`; `why` says it. An accepted pattern is checked on every agent of its scope on the next run — even when
+- **decisions**: `status` is `accepted` or `rejected`; `scope` is `platform` (every agent), `specialist`,
+  `orchestrator` or `type:<id>` (the specialists of a type — «tipo:<name>» in the workbook); `why` says it. An accepted pattern is checked on every agent of its scope on the next run — even when
   its share would no longer make it a pattern. A rejected one is shown and nobody is off it.
 
 ## The workbook back

package/skills/cast-list/references/keys.md

@@ -41,6 +41,10 @@ Every fact cast-list finds is a key. The keys below have a name; any other key k
 | Key | Name | Nome |
 |---|---|---|
 | `trigger:OnKnowledgeRequested` | Before searching knowledge | Antes de buscar no conhecimento |
+| `setting:semantic-search=on` | Semantic search on | Busca semântica ligada |
+| `setting:semantic-search=off` | Semantic search off | Busca semântica desligada |
+| `setting:web-browsing=on` | Web browsing on | Navegação na web ligada |
+| `setting:web-browsing=off` | Web browsing off | Navegação na web desligada |
 | `node:SearchAndSummarizeContent` | Generative answers from knowledge | Respostas generativas sobre o conhecimento |
 | `node:SearchKnowledgeSources` | Searches the knowledge sources | Busca nas fontes de conhecimento |
 | `yaml-only:triggerCondition` | Search condition only in YAML (the editor may erase it) | Condição de busca só no YAML (a tela pode apagar) |
@@ -63,6 +67,8 @@ Every fact cast-list finds is a key. The keys below have a name; any other key k
 
 | Key | Name | Nome |
 |---|---|---|
+| `setting:model-knowledge=on` | The model's general knowledge on | Conhecimento geral do modelo ligado |
+| `setting:model-knowledge=off` | The model's general knowledge off | Conhecimento geral do modelo desligado |
 | `instructions:present` | Has instructions | Tem instruções |
 | `node:LogCustomTelemetryEvent` | Logs telemetry | Registra telemetria |
 | `node:CSATQuestion` | Asks for satisfaction (CSAT) | Pergunta a satisfação (CSAT) |
@@ -70,6 +76,12 @@ Every fact cast-list finds is a key. The keys below have a name; any other key k
 | `model:<value>` | Model <value> | Modelo <valor> |
 | `auth:<value>` | Sign-in <value> | Login <valor> |
 
+## F. Text — F. Texto
+
+| Key | Name | Nome |
+|---|---|---|
+| `text:<value>` | Text: <value> | Texto: <valor> |
+
 ## Microsoft patterns — Padrões Microsoft
 
 | Key | Name | Nome |

package/skills/cast-list/references/profile.md

@@ -29,4 +29,39 @@ microsoft_patterns: on                 # off leaves the ms: facts out
 | `focus_areas` | none | Each a filter of the matrix. |
 | `ignore` | none | Keys that say nothing for this team. |
 
+## What to look for in the text, and the types
+
+```yaml
+rules:
+  # a condition and a «not»: the text says one thing, the setup another
+  - { id: knowledge-only, when: "text:knowledge-only", not: "setting:model-knowledge=on",
+      says: "Who asks for the knowledge alone has the model's general knowledge off" }
+markers:                               # JavaScript regular expressions; case does not matter
+  - { id: size, name: Answer size, in: instructions,
+      pattern: '(at most|up to|no máximo)\s*(\d+)\s*(bullets?|sentences?|frases?)', value: "$2 $3" }
+  - { id: no-emoji, name: No emojis, pattern: '(no|never use|sem)\s+emojis?' }
+  - { id: knowledge-only, name: Knowledge only, pattern: '(only|somente)[^.]{0,40}(knowledge|conhecimento)' }
+blocks:                                # the text the team pastes in every agent of a role
+  - id: links
+    name: Link formatting
+    role: specialist                   # the default
+    text: |
+      Links:
+      - Format links as [title](url), never the bare URL.
+types:                                 # a specialist gets every type whose «when» its facts match
+  - { id: transaction, name: transaction, when: { any: ["flow:*"] } }
+  - { id: guidance, name: guidance, when: { all: ["text:link-domain:*", "node:SearchAndSummarizeContent"], none: ["flow:*"] }, min_agents: 2 }
+```
+
+| Field | What it does |
+|---|---|
+| `rules[].when` / `has` / `not` | A rule is for the agents (of its `role`, or all) that have every key of `when`; it is broken when one lacks `has`, or has `not`. A key may end in `*`. A broken `not` rule is said as a contradiction. |
+| `markers` | `in`: `instructions` (the default), `descriptions` (what topics and actions tell the model) or `all`. With no `value`: a fact `text:<id>`. With a `value` (`$1`…`$9` from the regex): `text:<id>=<value>` — agents of a role that set it in different ways are told («unify?»), and one that sets it twice («which one holds?»). Two are built in: `text:link-domain:<host>` for each link in the instructions, `text:email`. In YAML, write a regex in single quotes. |
+| `blocks` | The official text. The family of blocks like it (half of it, at least) takes its id and name; every agent of `role` without it, or with a variation, is off it — with or without a majority. With no `blocks`, the blocks two agents or more share are still found, named by their first words. |
+| `types` | `when` with `all`, `any` (one of), `none`. A specialist may be of two types; the cast file's `types` for an agent win. Patterns are found within each type with its `min_agents` (2 unless said), scope `type:<id>`; a pattern of a type never blames who is not of it. A type with fewer agents is told, and compared in nothing. |
+
+A key in `when`, `has`, `not` or a type must start like a real kind of key (`references/keys.md`): a typo is
+`✗ profile:line`, as is a regex that does not compile, an unknown `in`, a type with no `when`, or a rule with
+nothing to check.
+
 The keys are the same in any language; only the screen words change with `--lang`.

package/skills/cast-list/scripts/build.mjs

@@ -82,11 +82,11 @@ const profile = option('--profile') ? read(resolve(option('--profile')), readPro
 const out = resolve(option('--out') ?? dirname(folder))
 const castFile = join(out, `${id}.cast.yaml`)
 const castText = existsSync(castFile) ? readFileSync(castFile, 'utf8') : undefined
-const cast = castText !== undefined ? read(castFile, readCast).cast : { ...(profile.name ? { name: profile.name } : {}), agents: [], declared: [], decisions: [] }
+const cast = castText !== undefined ? read(castFile, readCast).cast : { ...(profile.name ? { name: profile.name } : {}), agents: [], blocks: [], declared: [], decisions: [] }
 
 // ---- the way back: an edited workbook as the changes it proposes ----
 if (argv.includes('--from')) {
-  const edited = fromSheets(cast, readXlsx(readFileSync(resolve(option('--from')))))
+  const edited = fromSheets(cast, readXlsx(readFileSync(resolve(option('--from')))), Object.fromEntries(profile.types.map((t) => [t.id, t.name])))
   if (edited.problems.length) {
     for (const p of edited.problems) console.error(`✗ ${basename(option('--from'))}: ${p}`)
     process.exit(1)
@@ -145,8 +145,10 @@ const all = argv.includes('--all')
 const want = { html: all || argv.includes('--html'), xlsx: all || argv.includes('--xlsx'), lesson: all || argv.includes('--lesson') }
 if (!want.xlsx && !want.lesson) want.html = true
 mkdirSync(out, { recursive: true })
-// the cast file keeps this run's roles, under what people wrote in it
-const kept = { ...cast, agents: result.agents.map((a) => ({ id: a.id, role: a.role })) }
+// the cast file keeps this run's roles and blocks of text (so a block keeps its id across small edits), under what
+// people wrote in it; the types a person gave an agent stay, the ones the profile works out are not written
+const givenTypes = Object.fromEntries(cast.agents.filter((a) => a.types?.length).map((a) => [a.id, a.types]))
+const kept = { ...cast, agents: result.agents.map((a) => ({ id: a.id, role: a.role, ...(givenTypes[a.id] ? { types: givenTypes[a.id] } : {}) })), blocks: result.blocks.map((b) => ({ id: b.id, text: b.text })) }
 const castYaml = writeCast(kept, castText)
 writeFileSync(castFile, castYaml)
 console.log(`✓ cast      ${castFile}`)