@agfpd/voicetalk-runtime 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +81 -0
- package/bin/voicetalk-runtime +12 -0
- package/docs/README.md +31 -0
- package/docs/ru/README.md +30 -0
- package/package.json +29 -0
- package/src/cli.ts +1076 -0
- package/src/constants.ts +35 -0
- package/src/fsAtomic.ts +17 -0
- package/src/hostDocs.ts +87 -0
- package/src/manifest.ts +109 -0
- package/src/selfConfig.ts +129 -0
- package/src/selfInstall.ts +172 -0
- package/tsconfig.json +15 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 Artur Agafapudov
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
# voicetalk
|
|
2
|
+
|
|
3
|
+
**A live-voice channel for a team of AI agents — the voice-presence component of [iapeer](https://github.com/agfpd/iapeer).**
|
|
4
|
+
|
|
5
|
+
[](https://github.com/agfpd/voicetalk/actions/workflows/ci.yml)
|
|
6
|
+
[](./LICENSE)
|
|
7
|
+
[](#quick-start)
|
|
8
|
+
|
|
9
|
+
voicetalk gives a person presence in an [iapeer](https://github.com/agfpd/iapeer) agent team through live voice: the owner says a wake-word, speaks, and an agent answers out loud from the host's speaker. To the agent, the person is an ordinary peer it reaches with `send_to_peer` — voicetalk turns speech into an inbound message and the agent's reply into spoken audio. It is the third runtime of iapeer after `telegram-runtime` and `notifier-runtime`, and the same single identity an agent already has across Claude, Codex, and Telegram.
|
|
10
|
+
|
|
11
|
+
> **Built for iapeer.** It isn't a standalone voice assistant — it runs only inside [iapeer](https://github.com/agfpd/iapeer), alongside `telegram-runtime` and `notifier-runtime`. It's an iapeer runtime whose messages travel over iapeer's own routing; the speech-to-text and text-to-speech themselves live in a separate voice service (`voice-connect`), which voicetalk consumes.
|
|
12
|
+
|
|
13
|
+
## How it works
|
|
14
|
+
|
|
15
|
+
```text
|
|
16
|
+
person speaking aloud agent (Claude/Codex)
|
|
17
|
+
│ "Boris, …" (wake-word + speech) │ send_to_peer(arthur, "…")
|
|
18
|
+
▼ ▼
|
|
19
|
+
┌──────────────────────────────────────────────────────────┐
|
|
20
|
+
│ voicetalk — the voice channel │
|
|
21
|
+
│ inbound: microphone → wake-word → STT → recipient peer │
|
|
22
|
+
│ outbound: peer → TTS → host speaker │
|
|
23
|
+
│ open-mic follow-up · endpointing · earcons │
|
|
24
|
+
└──────────────────────────────────────────────────────────┘
|
|
25
|
+
speech ↔ text via voice-connect (STT / TTS)
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
## Quick start
|
|
29
|
+
|
|
30
|
+
> Status: **text caркас (Фаза 2).** The bidirectional router loop works end to end over text; the audio touchpoints (wake-word, STT, TTS) are stubbed and land in Фаза 3 — see the roadmap below.
|
|
31
|
+
|
|
32
|
+
You will need a working iapeer install (and, for Фаза 3, the `voice-connect` voice service).
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
npx @agfpd/voicetalk-runtime # install: binary on PATH + runtime manifest
|
|
36
|
+
iapeer create <person> --runtime voicetalk # give a person a voice endpoint (operator-add)
|
|
37
|
+
voicetalk-runtime doctor # check the runtime + this peer's binding
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
Once a peer is created, the always-on `voicetalk-runtime run` router pumps IAP
|
|
41
|
+
envelopes both directions. In Фаза 2 the inbound audio source is stubbed by a local
|
|
42
|
+
injector you can drive by hand — the round trip works without a microphone:
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
voicetalk-runtime interface --wake-word "hey jarvis" --device mic0 # set the binding
|
|
46
|
+
# (run is launched by the foundation under the always-on supervisor)
|
|
47
|
+
voicetalk-runtime say --peer linus "what's the build status" # inject an utterance (mic+STT stand-in)
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
An outbound peer reply arrives as an `<iap>` envelope on the router's stdin and is
|
|
51
|
+
spoken by the AudioSink — a logging stub today, `voice-connect` TTS in Фаза 3.
|
|
52
|
+
|
|
53
|
+
## What makes it different
|
|
54
|
+
|
|
55
|
+
- **Transparent channel.** Agents get no microphone or speaker tools — to an agent, the person is just a named peer. The same `send_to_peer` reaches a human by voice, by Telegram, or by an AI agent alike.
|
|
56
|
+
- **One identity, another runtime.** Voice is not a bolt-on assistant; it is one more runtime of the peer's single identity (`from-runtime=voicetalk`), exactly as Telegram is.
|
|
57
|
+
- **Modality framing for a naive agent.** An agent has no senses — only envelope text. voicetalk marks the inbound envelope so a peer with no knowledge of the system answers in the right modality ("spoken, live — reply by voice, briefly").
|
|
58
|
+
- **Voice stays out of the core.** Speech-to-text and text-to-speech live in the shared `voice-connect` service (multi-provider, one place to configure), not inside this runtime and not inside the iapeer foundation.
|
|
59
|
+
- **Conversational turn-taking.** A wake-word only opens a conversation; after a reply, an open-mic window lets the next utterance continue without re-triggering. Endpointing and earcons are owned here, inside the audio session — the agent only sees the next message.
|
|
60
|
+
|
|
61
|
+
## What it does not do (yet)
|
|
62
|
+
|
|
63
|
+
- No audio yet: the wake-word, STT, and TTS touchpoints are stubbed (the inbound source is a local socket injector; the outbound sink logs instead of speaking). The bidirectional **router loop itself works** over text. Audio lands in Фаза 3 via `voice-connect`.
|
|
64
|
+
- Foundation integration is a coordinated step: the `voicetalk` launch-adapter and runtime classification on the iapeer side gate `iapeer create --runtime voicetalk` (Фаза 1).
|
|
65
|
+
- Single host, single owner, local microphone and speaker. Multi-device and multi-owner are out of scope for the MVP.
|
|
66
|
+
|
|
67
|
+
## Roadmap
|
|
68
|
+
|
|
69
|
+
- **Фаза 0 — Scaffold.** Package skeleton, CLI stub, contract constants. **(done)**
|
|
70
|
+
- **Фаза 1 — Foundation integration (iapeer).** `voicetalk` launch-adapter, runtime classification, `iapeer create --runtime voicetalk`. **(adapter code-complete; deploy coordinated with Фаза 2)**
|
|
71
|
+
- **Фаза 2 — Runtime skeleton.** `runtime.json` manifest + `selfConfig` hook; `interfaces.voicetalk` schema; bidirectional router loop with a text-only IAP round-trip (audio stubbed). **(done)**
|
|
72
|
+
- **Фаза 3 — Voice pipeline.** Always-on wake-word → STT (inbound), TTS → speaker (outbound) via `voice-connect`; modality framing.
|
|
73
|
+
- **Фаза 4 — Latency and live acceptance.** Tune the chain, conversational round-trip live.
|
|
74
|
+
|
|
75
|
+
## Documentation
|
|
76
|
+
|
|
77
|
+
[`docs/`](docs/README.md) — what it is and how it will work (English; Russian in [`docs/ru/`](docs/ru/README.md)). This repository is the implementation.
|
|
78
|
+
|
|
79
|
+
## License
|
|
80
|
+
|
|
81
|
+
Apache-2.0. Platform: macOS. voicetalk is the voice-presence runtime for the [iapeer](https://github.com/agfpd/iapeer) ecosystem — a component of iapeer, not a standalone system.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
#!/usr/bin/env bash
|
|
2
|
+
set -euo pipefail
|
|
3
|
+
|
|
4
|
+
# Resolve symlinks so the bin works when invoked through ~/.local/bin/voicetalk-runtime
|
|
5
|
+
SOURCE="${BASH_SOURCE[0]}"
|
|
6
|
+
while [ -L "$SOURCE" ]; do
|
|
7
|
+
DIR="$(cd "$(dirname "$SOURCE")" && pwd)"
|
|
8
|
+
SOURCE="$(readlink "$SOURCE")"
|
|
9
|
+
[[ "$SOURCE" != /* ]] && SOURCE="$DIR/$SOURCE"
|
|
10
|
+
done
|
|
11
|
+
ROOT="$(cd "$(dirname "$SOURCE")/.." && pwd)"
|
|
12
|
+
exec bun "$ROOT/src/cli.ts" "$@"
|
package/docs/README.md
ADDED
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# voicetalk documentation
|
|
2
|
+
|
|
3
|
+
voicetalk is the voice-presence runtime of [iapeer](https://github.com/agfpd/iapeer):
|
|
4
|
+
a person speaks to the agent team aloud (wake-word + microphone) and hears replies
|
|
5
|
+
from the host speaker, as one more runtime of the peer's single identity.
|
|
6
|
+
|
|
7
|
+
> Status: scaffold (Фаза 0). The audio pipeline is not implemented yet. This
|
|
8
|
+
> documentation describes the design; it grows as the runtime is built out across
|
|
9
|
+
> Фазы 1–4. See the root [README](../README.md) for the roadmap.
|
|
10
|
+
|
|
11
|
+
## Contents
|
|
12
|
+
|
|
13
|
+
- Overview — what voicetalk is and how it fits the iapeer runtime contract.
|
|
14
|
+
- Quick start — operator flow (`iapeer create --runtime voicetalk`).
|
|
15
|
+
- Architecture — the two-layer split (foundation adapter + runtime binary) and the
|
|
16
|
+
`voice-connect` voice service it consumes.
|
|
17
|
+
- Configuration — `interfaces.voicetalk` (`wake_word`, `device`).
|
|
18
|
+
|
|
19
|
+
These pages are written as each phase lands. Russian translation lives in
|
|
20
|
+
[`ru/`](ru/README.md).
|
|
21
|
+
|
|
22
|
+
## Design references
|
|
23
|
+
|
|
24
|
+
The full design lives in the team's shared memory (iapeer-memory):
|
|
25
|
+
|
|
26
|
+
- «Описание voicetalk» — project description.
|
|
27
|
+
- «План voicetalk» — phases.
|
|
28
|
+
- «Голосовой слой voice-connect — единый сервис, core плюс два фасада» — the voice
|
|
29
|
+
service decision.
|
|
30
|
+
- «Контракт presence-рантайма в iapeer 0.4.x — два слоя, router-модель» — the
|
|
31
|
+
foundation contract this runtime implements.
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
# Документация voicetalk
|
|
2
|
+
|
|
3
|
+
voicetalk — голосовой presence-рантайм [iapeer](https://github.com/agfpd/iapeer):
|
|
4
|
+
человек говорит флоту агентов вслух (wake-word + микрофон) и слышит ответы из
|
|
5
|
+
динамика хоста — это ещё один рантайм единой личности пира.
|
|
6
|
+
|
|
7
|
+
> Статус: каркас (Фаза 0). Голосовой пайплайн ещё не реализован. Документация
|
|
8
|
+
> описывает дизайн и наполняется по мере сборки рантайма в Фазах 1–4. Дорожная
|
|
9
|
+
> карта — в корневом [README](../../README.md).
|
|
10
|
+
|
|
11
|
+
## Содержание
|
|
12
|
+
|
|
13
|
+
- Обзор — что такое voicetalk и как он вписывается в контракт рантаймов iapeer.
|
|
14
|
+
- Быстрый старт — операторский поток (`iapeer create --runtime voicetalk`).
|
|
15
|
+
- Архитектура — двухслойность (foundation-адаптер + бинарь рантайма) и голосовой
|
|
16
|
+
сервис `voice-connect`, который voicetalk потребляет.
|
|
17
|
+
- Настройка — `interfaces.voicetalk` (`wake_word`, `device`).
|
|
18
|
+
|
|
19
|
+
Страницы пишутся по мере прохождения фаз.
|
|
20
|
+
|
|
21
|
+
## Источники дизайна
|
|
22
|
+
|
|
23
|
+
Полный дизайн — в общей памяти команды (iapeer-memory):
|
|
24
|
+
|
|
25
|
+
- «Описание voicetalk» — описание проекта.
|
|
26
|
+
- «План voicetalk» — фазы.
|
|
27
|
+
- «Голосовой слой voice-connect — единый сервис, core плюс два фасада» — решение по
|
|
28
|
+
голосовому сервису.
|
|
29
|
+
- «Контракт presence-рантайма в iapeer 0.4.x — два слоя, router-модель» — контракт
|
|
30
|
+
foundation, который реализует этот рантайм.
|
package/package.json
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@agfpd/voicetalk-runtime",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Voice runtime-router for IAP peers.",
|
|
5
|
+
"license": "Apache-2.0",
|
|
6
|
+
"type": "module",
|
|
7
|
+
"bin": {
|
|
8
|
+
"voicetalk-runtime": "bin/voicetalk-runtime"
|
|
9
|
+
},
|
|
10
|
+
"files": [
|
|
11
|
+
"bin/",
|
|
12
|
+
"src/",
|
|
13
|
+
"docs/*.md",
|
|
14
|
+
"docs/ru/",
|
|
15
|
+
"tsconfig.json"
|
|
16
|
+
],
|
|
17
|
+
"scripts": {
|
|
18
|
+
"start": "bun src/cli.ts run",
|
|
19
|
+
"self-install": "bun src/cli.ts self-install",
|
|
20
|
+
"self-config": "bun src/cli.ts self-config",
|
|
21
|
+
"doctor": "bun src/cli.ts doctor --json",
|
|
22
|
+
"test": "bun test",
|
|
23
|
+
"typecheck": "tsc --noEmit"
|
|
24
|
+
},
|
|
25
|
+
"devDependencies": {
|
|
26
|
+
"@types/bun": "latest",
|
|
27
|
+
"typescript": "latest"
|
|
28
|
+
}
|
|
29
|
+
}
|