Repository navigation
Expand file tree
/
Copy pathbacklog.json
More file actions
463 lines (463 loc) · 27.8 KB
/
Copy pathbacklog.json
File metadata and controls
463 lines (463 loc) · 27.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
[
{
"key": "runtime-contract",
"title": "[RFC] Define the AL2023 runtime contract and redistribution policy",
"milestone": 2,
"labels": [
"type:rfc",
"area:runtime",
"priority:p0",
"status:ready"
],
"depends": [],
"scope": "Settle the initial static/base contract before rootfs implementation. Start with official AL2023 packages and a BuildKit multi-stage builder, with scratch final images. Decide file boundaries, glibc/NSS behavior, CA paths, UTC/locale policy, non-root identity, supported workloads, and package-license/source handling. Java, Python, and Node.js are committed language deliverables, specified in the separate language-runtime RFC; a standalone cc image and general C++ application support are excluded.",
"acceptance": [
"Record accepted static/base contents and exclusions, including whether base contains OpenSSL libraries",
"Specify UID/GID 65532, working directory, /tmp permissions, read-only-rootfs behavior, CA bundle paths, NSS configuration, UTC, and locale behavior",
"Document compatible AL2023-linked workloads and limitations for arbitrary glibc or musl binaries",
"Choose verified RPM extraction or installroot assembly and document scriptlet/configuration handling",
"Define project licensing versus redistributed RPM licenses, notices, and source-availability obligations",
"Review the proposed architecture and record unresolved risks as follow-up issues",
"Record static/base as shared foundations, Java/Python/Node.js as required v1.0 runtime variants, and the removal of standalone C++ support"
],
"validation": "Design review against official AL2023 package metadata and at least one static Go and one dynamic C workload. Record a decision, rationale, and evidence in docs/."
},
{
"key": "language-runtimes",
"title": "[RFC] Define committed Java, Python, and Node.js runtime contracts",
"milestone": 2,
"labels": [
"type:rfc",
"area:runtime",
"priority:p0",
"status:triage"
],
"depends": [
"runtime-contract"
],
"scope": "Java, Python, and Node.js are committed v1.0 deliverables. Select one maintained major/minor line per language from official packages available in the pinned AL2023 release. Specify versioned image names, exact executable paths, dependency closure, and application packaging contracts. This RFC settles implementation details; it must not reduce support to a single optional language.",
"acceptance": [
"Record an initial supported version line for each of Java, Python, and Node.js based on pinned AL2023 package availability, upstream support, and AL2023 package support",
"Define Java using Amazon Corretto headless runtime packages, executable JAR startup, JAVA_HOME, JVM truststore handling, and required native libraries; build tooling stays in builders",
"Define Python interpreter/stdlib paths, a deterministic application dependency location and sys.path, version-matched native wheel ABI, and builder-only pip/venv packaging",
"Define Node.js executable/version paths, ESM/CommonJS behavior, builder-installed production node_modules, native addon ABI, and builder-only npm/package tooling",
"Require separate java/python/nodejs images on linux/amd64 and linux/arm64, with the shared non-root and shell-free contract",
"Exclude a standalone cc image and general C++ workload support while permitting audited native libraries required by the selected language runtimes",
"Record license, source delivery, size, update ownership, and lifecycle requirements for all three runtime lines"
],
"validation": "Review official AL2023/Corretto package metadata and support statements, then document a concrete runtime/file/ABI matrix and minimal packaging examples for each language. Do not pick versions from floating system alternatives."
},
{
"key": "locked-inputs",
"title": "[Task] Lock AL2023 builder and RPM inputs with provenance",
"milestone": 2,
"labels": [
"type:task",
"area:build",
"priority:p0",
"status:triage"
],
"depends": [
"runtime-contract",
"language-runtimes"
],
"scope": "Create a versioned input lock and resolver for official AL2023 packages. Pin a builder index digest separately from the DNF releasever. Capture architecture-specific package versions, checksums, signatures, repository metadata, and license/source references. Cover selected Java, Python, and Node.js packages as well as static/base foundations; maintain per-variant lock sections and preserve a path to incremental runtime additions.",
"acceptance": [
"Pin an official builder digest and an explicit AL2023 releasever; release mode rejects floating latest inputs",
"Record per-architecture package NEVRAs, checksums, dependency closure, signature verification, and repository references",
"Disable weak dependencies deliberately and document necessary exceptions",
"Produce a package-to-file/provenance inventory suitable for final-image SBOM generation",
"Document a repeatable lock update command and reviewable package diff",
"Represent the selected Java/Python/Node.js versions, exact runtime paths, and per-variant package closure; reject unresolved alternatives symlinks"
],
"validation": "Resolve twice only as the reproducibility experiment, compare the locked package set, and prove that a modified checksum or invalid/untrusted signature fails closed."
},
{
"key": "rootfs",
"title": "[Task] Assemble amd64 static and base rootfs from verified AL2023 packages",
"milestone": 2,
"labels": [
"type:task",
"area:build",
"priority:p0",
"status:triage"
],
"depends": [
"runtime-contract",
"locked-inputs"
],
"scope": "Implement allowlist-driven rootfs assembly and scratch Dockerfile targets for static and base on amd64. Avoid copying the complete builder filesystem. Preserve required licenses, runtime configuration, ownership, and symlinks.",
"acceptance": [
"Build static and base targets from locked inputs with a documented single entry command",
"Give every copied file a reviewed source/provenance entry and reject unexpected or missing files",
"Resolve ELF interpreter and transitive shared-library dependencies, including architecture-specific symlinks",
"Include the accepted CA/NSS/user/temporary-directory contract and default to numeric non-root UID/GID",
"Exclude shells, package managers, RPM databases, compilers, and build caches from production outputs",
"Emit a final file inventory with checksums, modes, ownership, and symlink targets"
],
"validation": "Inspect an exported final rootfs; compare it with the allowlist and run minimal static and dynamic binaries. Do not use an untrusted binary's ldd execution as the audit mechanism."
},
{
"key": "runtime-tests",
"title": "[Task] Prove the final-image runtime and absent-tool contract",
"milestone": 2,
"labels": [
"type:task",
"area:runtime",
"priority:p0",
"status:triage"
],
"depends": [
"rootfs"
],
"scope": "Add meaningful black-box probes against final static/base images: pure static Go and AL2023-linked C, with a local controlled service for DNS/TLS behavior. Keep fixtures separate from production images.",
"acceptance": [
"Static Go and dynamically linked C probes run in their intended variants with the expected non-root identity",
"Validate DNS/NSS resolution, CA trust with a controlled TLS endpoint, UTC/time behavior, and passwd/group lookup",
"Run supported workloads with read-only rootfs, an explicit temporary mount, all capabilities dropped, and no-new-privileges",
"Assert that shell and package-manager execution is unavailable and inspect the complete rootfs for forbidden tools",
"Verify exec-form startup, signal handling, and exit-code behavior without assuming a shell or an init binary",
"Document supported and deliberately unsupported workloads"
],
"validation": "Run the contract suite on linux/amd64 with a fresh final-image build. Capture exact build inputs and test logs. Use deterministic local test infrastructure rather than public endpoint availability."
},
{
"key": "multiarch",
"title": "[Task] Add arm64 builds and architecture-specific runtime validation",
"milestone": 3,
"labels": [
"type:task",
"area:build",
"priority:p1",
"status:triage"
],
"depends": [
"runtime-tests",
"locked-inputs"
],
"scope": "Extend the prototype to linux/arm64, with explicit mapping to AL2023 aarch64 packages and loader paths. Support local emulation for convenience and documented native execution for release qualification.",
"acceptance": [
"Build both static/base variants for linux/amd64 and linux/arm64 from locked architecture-correct RPMs",
"Reject mixed-architecture packages and validate each ELF interpreter and library closure",
"Pass the same runtime contract on both architectures",
"Document emulation limitations and obtain native arm64 runtime evidence before stable release",
"Assemble and inspect an OCI index without publishing production tags"
],
"validation": "Run per-architecture final-container probes and inspect index platform descriptors. Record whether each execution was native or emulated."
},
{
"key": "pr-ci",
"title": "[Task] Add unprivileged PR image builds and runtime CI",
"milestone": 3,
"labels": [
"type:task",
"area:ci",
"priority:p1",
"status:triage"
],
"depends": [
"runtime-tests",
"multiarch"
],
"scope": "Build/test changed image definitions on pull requests and main without registry publishing credentials. Keep privileged release work in a separate future workflow.",
"acceptance": [
"CI covers static/base on both architectures initially and provides an extensible variant/version matrix for the language-validation issue",
"Pull-request jobs use read-only permissions and do not expose release credentials to fork code",
"Pin action dependencies and document cache keys that include lock inputs and architecture",
"Add path-aware execution without leaving required checks permanently pending when paths are skipped",
"Make the implemented build/runtime checks required for main after their first successful runs",
"Document local commands that reproduce the CI checks"
],
"validation": "Exercise one passing workload and one intentionally failing fixture in a temporary branch/PR, confirm check behavior, then remove the intentional failure before merge."
},
{
"key": "repro-size",
"title": "[Task] Measure reproducibility and establish image-size budgets",
"milestone": 3,
"labels": [
"type:task",
"area:build",
"priority:p1",
"status:triage"
],
"depends": [
"multiarch",
"pr-ci"
],
"scope": "Measure normalized rootfs reproducibility separately from image/index digest reproducibility. Establish evidence-based size budgets per variant/architecture against official AL2023 base and minimal baselines. This milestone establishes static/base baselines; the language-validation issue extends measurements and budgets to Java, Python, and Node.js.",
"acceptance": [
"Compare clean builds from identical locked inputs and explain any rootfs differences",
"Normalize ordering, modes, ownership, timestamps, and archive metadata where supported",
"Report OCI digest differences caused by provenance or build metadata separately from runtime-file differences",
"Record compressed transfer size, unpacked size, file count, and package count with measurement definitions",
"Set reviewed size-regression budgets from measured results rather than guessed size claims",
"Publish a baseline report and make material regressions visible in CI"
],
"validation": "Run the documented paired clean-build experiment once for each supported variant/architecture and store the manifest comparison and size report."
},
{
"key": "java",
"title": "[Feature] Build a distroless-like Amazon Corretto Java runtime image",
"milestone": 6,
"labels": [
"type:feature",
"area:runtime",
"priority:p1",
"status:triage",
"runtime:java"
],
"depends": [
"language-runtimes",
"locked-inputs",
"multiarch"
],
"scope": "Implement the java variant from the accepted Amazon Corretto headless runtime contract and official pinned AL2023 packages. Keep javac, Maven, Gradle, and other build tooling in a separate builder; ship audited runtime libraries and data only.",
"acceptance": [
"Build the selected versioned Java image for linux/amd64 and linux/arm64 from per-variant locks and a file allowlist",
"Run an executable JAR directly with an exec-form java entrypoint as UID/GID 65532",
"Validate JAVA_HOME, required JVM/native libraries, truststore/CA behavior, DNS, UTC, signals, and exit status",
"Run a representative headless Java service with read-only rootfs, an explicit tmpfs, dropped capabilities, and no-new-privileges",
"Exclude shell, package managers, javac, Maven, Gradle, JDK development artifacts, and unneeded GUI components while preserving required license/source material",
"Produce package/file evidence and a runnable multi-stage JAR example"
],
"validation": "Run a headless executable-JAR and controlled TLS/DNS fixture against final images on both architectures, including required runtime-loaded libraries and hardened-container settings."
},
{
"key": "python",
"title": "[Feature] Build a distroless-like Python runtime image",
"milestone": 6,
"labels": [
"type:feature",
"area:runtime",
"priority:p1",
"status:triage",
"runtime:python"
],
"depends": [
"language-runtimes",
"locked-inputs",
"multiarch"
],
"scope": "Implement the python variant using the selected versioned AL2023 interpreter and standard library. Define a stable application dependency directory/sys.path contract; install application dependencies in a matching builder, without pip or a shell in the final image.",
"acceptance": [
"Build the selected versioned Python image for both supported architectures with correct interpreter/stdlib and runtime-loaded shared-library closure",
"Run scripts and module entrypoints with explicit interpreter paths and deterministic sys.path/application package locations",
"Validate ssl, ctypes/dynamic loading where supported, encodings, importlib, DNS, UTC, and interpreter-required extension modules",
"Build and run one representative native extension in an AL2023-compatible builder with matching Python version and target architecture; document supported wheel/ABI boundaries",
"Run non-root and with read-only rootfs, disable or redirect bytecode/cache writes, and support a documented writable temporary mount",
"Keep pip, ensurepip installer payloads, compiler/header toolchains, package managers, and shells out of the final runtime; record deliberate stdlib exclusions",
"Provide a reproducible multi-stage dependency-installation example and complete package/file/license evidence"
],
"validation": "Run stdlib imports, an application dependency import, a version-matched native-extension fixture, and controlled TLS/DNS probes against final images on both architectures."
},
{
"key": "nodejs",
"title": "[Feature] Build a distroless-like Node.js runtime image",
"milestone": 6,
"labels": [
"type:feature",
"area:runtime",
"priority:p1",
"status:triage",
"runtime:nodejs"
],
"depends": [
"language-runtimes",
"locked-inputs",
"multiarch"
],
"scope": "Implement the nodejs variant from selected official versioned AL2023 Node.js packages. Copy production node_modules from a compatible architecture/version-matched builder and start the application with node directly; npm is a builder tool.",
"acceptance": [
"Build the selected Node.js version on linux/amd64 and linux/arm64 with explicit executable paths and audited shared-library/data dependencies",
"Run both CommonJS and ESM entrypoints directly with node, without npm start or shell wrappers",
"Document and validate production node_modules layout and lockfile-based installation in a matching builder",
"Build and execute a representative native addon with the documented Node ABI/N-API, AL2023 toolchain, and target architecture",
"Validate Node/OpenSSL CA policy, DNS, UTC/Intl scope, signals, exit status, and a representative HTTP service",
"Run as UID/GID 65532 with read-only rootfs and dropped capabilities; exclude npm, npx, corepack, package managers, compilers, and shells from production images",
"Emit package/file/license evidence and a runnable multi-stage application example"
],
"validation": "Run ESM/CommonJS, controlled HTTP/TLS/DNS, and native-addon fixtures against final images on both architectures with the documented hardened settings."
},
{
"key": "language-validation",
"title": "[Task] Qualify all three language images in CI and release gates",
"milestone": 6,
"labels": [
"type:task",
"area:ci",
"priority:p0",
"status:triage"
],
"depends": [
"java",
"python",
"nodejs",
"pr-ci",
"repro-size"
],
"scope": "Extend the established static/base contract to java/python/nodejs. All three language variants are mandatory before v1.0 publication; do not ship them as untested optional artifacts.",
"acceptance": [
"Run a variant/version/architecture CI matrix covering static, base, java, python, and nodejs with their specific workload probes",
"Record native execution evidence on both architectures for all language variants before stable release",
"Measure per-language size budgets and reproducibility using the same definitions as static/base; validate interpreter/JVM/runtime-loaded dependencies",
"Apply shell/package-manager/build-tool absence checks and hardened non-root execution to every variant, accounting for legitimate Java/Python/Node executables",
"Include complete language runtime and native library identities in SBOMs, scans, notices, source delivery, and provenance; capture any scanner detection limitations",
"Block stable release if any committed language variant fails its runtime, security, signature/evidence, or lifecycle contract",
"Document builders, version/ABI boundaries, update ownership, and consumer examples for all three languages"
],
"validation": "Execute each language workload and native dependency fixture in the CI matrix, confirm a failing language variant blocks release, and retain per-variant runtime/size/inventory evidence."
},
{
"key": "sbom",
"title": "[Task] Produce SBOM, provenance, and complete redistribution evidence",
"milestone": 4,
"labels": [
"type:task",
"area:security",
"priority:p0",
"status:triage"
],
"depends": [
"locked-inputs",
"repro-size",
"language-validation"
],
"scope": "Generate per-architecture component evidence from the actual included files, preserving AL2023 identity even though the runtime has no RPM database. Cover project and component license obligations. Include static, base, java, python, and nodejs, including interpreter modules, JVM runtime data, and necessary native libraries.",
"acceptance": [
"Generate machine-readable SBOMs with exact included package versions, file ownership, checksums, and source references",
"Distinguish complete installed RPM contents from the subset actually shipped in the runtime",
"Attach verifiable build provenance covering source commit, builder digest, releasever, tool versions, and lock inputs",
"Include required license texts/notices and fulfill the accepted source-availability approach",
"Validate SBOM subjects against final image digests and document consumer retrieval",
"Test at least one partial-package case so inventory does not falsely claim an entire RPM is present"
],
"validation": "Inspect the SBOM against the rootfs/package-to-file map, verify digest subjects, and review license/source completeness for every redistributed component."
},
{
"key": "vulnerability-policy",
"title": "[Task] Add AL2023-aware vulnerability scanning and exception policy",
"milestone": 4,
"labels": [
"type:task",
"area:security",
"priority:p0",
"status:triage"
],
"depends": [
"sbom"
],
"scope": "Choose and pin a scanner that recognizes AL2023 package identity from the final image/evidence. Define stable-release gates and a reviewable, expiring exception mechanism.",
"acceptance": [
"Demonstrate correct AL2023 detection and package versions without a runtime RPM database",
"Compare representative scanner results with ALAS advisories and backported-fix versions",
"Fail stable releases on applicable critical/high findings unless a reviewed, scoped, owned, expiring exception exists",
"Fail closed for scanner/database errors and document database age policy",
"Record scan tool/database versions, results, applicability decisions, and exception expiry checks",
"Document false-positive handling without claiming zero CVEs from missing metadata",
"Cover all committed variants and distinguish base OS, Java, Python, Node.js, and native-library detection from downstream application dependencies"
],
"validation": "Use known affected and fixed AL2023 package fixtures plus expired/valid exception fixtures to demonstrate gate behavior."
},
{
"key": "release",
"title": "[Task] Publish signed immutable multi-architecture GHCR releases",
"milestone": 4,
"labels": [
"type:task",
"area:release",
"priority:p0",
"status:triage"
],
"depends": [
"sbom",
"vulnerability-policy",
"pr-ci",
"language-validation"
],
"scope": "Agree on versioned image/tag naming and implement trusted GHCR promotion for static, base, java, python, and nodejs. Proposed suffixes use those variant names under ghcr.io/rambow-cloud/amazon-linux-distroless; validate package permissions and naming before adoption. No stable release is complete with a committed language missing.",
"acceptance": [
"Document image names, versioned tags, optional moving aliases, digest consumption, prereleases, and immutability policy",
"Publish only after all required per-architecture checks, size gates, evidence generation, and scans pass",
"Restrict release inputs to reviewed protected-branch commits and validate tag/commit relationships",
"Sign image/index subjects using a documented identity and publish retrievable SBOM/provenance evidence",
"Use least-privilege publishing/OIDC permissions and prevent untrusted PR code from obtaining them",
"Test consumer signature/provenance verification and rejection of an unexpected identity",
"Document failed-publication recovery and rollback to a previous verified digest",
"Publish and verify static/base/java/python/nodejs with explicit runtime-version and architecture references; do not label the aggregate multi-license image solely Apache-2.0"
],
"validation": "Perform a tagged prerelease/candidate end-to-end before any stable release. Verify both platform pulls, index signatures, evidence subjects, access permissions, and documented rollback."
},
{
"key": "updates",
"title": "[Task] Automate reviewed AL2023 refreshes and document support policy",
"milestone": 4,
"labels": [
"type:task",
"area:release",
"priority:p1",
"status:triage"
],
"depends": [
"release"
],
"scope": "Implement a reviewed update-detection process for upstream repository/builder changes, security fixes, and pinned tooling. Define achievable maintenance commitments before stable release. Track selected Corretto, Python, and Node.js runtime versions and native-library updates as part of the supported image matrix.",
"acceptance": [
"Detect upstream AL2023 release and digest changes and create a scoped update issue or PR without silently publishing",
"Include package/version/license/size diffs and relevant ALAS security impact in update proposals",
"Run the full release evidence and runtime gates on refreshes",
"Document supported tags, maintenance window, update cadence, vulnerability triage expectations, and end-of-life handling",
"Distinguish upstream AL2023/package support from this project's own support commitments",
"Document rollback and emergency fix procedures; avoid promising an unstaffed response SLA",
"Document support and replacement policy for every selected language version and trigger reviewed refreshes for runtime as well as AL2023 updates"
],
"validation": "Exercise the detector with a controlled old/new lock fixture, confirm duplicate detection, and walk through one candidate refresh and rollback. No schedule is enabled until the implementation is reviewed."
},
{
"key": "release-docs",
"title": "[Task] Deliver consumer examples and v1.0 release acceptance evidence",
"milestone": 4,
"labels": [
"type:task",
"area:docs",
"priority:p1",
"status:triage"
],
"depends": [
"release",
"updates"
],
"scope": "Document how consumers build applications against the runtime contract, pin digests, verify evidence, and operate without a shell. Collect a stable-release acceptance checklist. Java, Python, and Node.js examples and their runtime-version contracts are required stable-release deliverables.",
"acceptance": [
"Provide tested Java executable-JAR, Python dependency/native-extension, and Node.js ESM/CommonJS/native-addon multi-stage examples on both architectures; retain static/base probes as foundation examples",
"Show exec-form entrypoints, non-root operation, read-only rootfs, writable mounts, and digest pinning",
"Document CA/NSS/timezone/locale behavior, compatibility boundaries, debugging approach, and troubleshooting",
"Provide copyable signature/SBOM/provenance verification instructions tied to the actual release identity",
"Publish a v1.0 acceptance report with native runtime evidence on both architectures, size baselines, scan results, and support policy",
"Remove planning-only placeholders and clearly identify any deferred optional functionality"
],
"validation": "Build and run every published example against candidate release digests and follow the verification instructions from a clean consumer environment."
},
{
"key": "debug",
"title": "[RFC] Define isolated debugging without expanding production images",
"milestone": 5,
"labels": [
"type:rfc",
"area:runtime",
"priority:p2",
"status:triage"
],
"depends": [
"release-docs"
],
"scope": "Compare ephemeral debug containers with an explicitly separate debug image for static, base, java, python, and nodejs. Do not add a shell to any production runtime image.",
"acceptance": [
"Compare approaches for local Docker and Kubernetes with concrete debugging scenarios",
"Define access, tool provenance, component licenses, architecture coverage, image size, and update ownership",
"Document a clear distinction between production images and any separate debug artifacts",
"Verify troubleshooting steps without requiring production image modification",
"Record an accepted choice or explicitly defer debug-image publication"
],
"validation": "Demonstrate a failed-startup or DNS/TLS troubleshooting scenario using the proposed isolated approach."
}
]