diff --git a/.github/workflows/dotnet-integration-tests.yml b/.github/workflows/dotnet-integration-tests.yml index 98514d992101..6643b10c12a0 100644 --- a/.github/workflows/dotnet-integration-tests.yml +++ b/.github/workflows/dotnet-integration-tests.yml @@ -11,6 +11,9 @@ on: pull_request: branches: [ "main" ] +permissions: + contents: read + jobs: integration-tests: strategy: @@ -22,12 +25,12 @@ jobs: - uses: actions/checkout@v3 with: clean: true - + - name: Setup .NET uses: actions/setup-dotnet@v3 with: dotnet-version: 6.0.x - + - name: Find projects shell: bash run: echo "projects=$(find ./dotnet -type f -name "*IntegrationTests.csproj" | tr '\n' ' ')" >> $GITHUB_ENV diff --git a/GLOSSARY.md b/GLOSSARY.md index f984bf44d6c2..24ffc2e37927 100644 --- a/GLOSSARY.md +++ b/GLOSSARY.md @@ -5,7 +5,7 @@ commonly used terms **Semantic Kernel (SK)** - The orchestrator that fulfills a user's ASK with SK's available SKILLS. -**Ask**- What a user requests to the Semantic Kernel to help achieve the user's goal. +**Ask** - What a user requests to the Semantic Kernel to help achieve the user's goal. - "We make ASKs to the SK" @@ -17,16 +17,22 @@ commonly used terms - "The Office SKILL has many FUNCTIONs" -**Native Function** - expressed in the conventions of the computing language (Python, C#, Typescript) +**Native Function** - expressed with traditional computing language (C#, Python, Typescript) and easily integrates with SK -**Semantic Function** - expressed in natural language in a text file "skprompt.txt" using SK's Prompt -Template. Each semantic function is defined by a unique prompt template file, developed using modern +**Semantic Function** - expressed in natural language in a text file "*skprompt.txt*" using SK's Prompt +Template language. Each semantic function is defined by a unique prompt template file, developed using modern **prompt engineering** techniques. +**Memory** - a collection of semantic knowledge, based on facts, events, documents, indexed with **embeddings**. + +

+image +

+ The kernel is designed to encourage **function composition**, allowing users to combine multiple functions (native and semantic) into a single pipeline.

-image +image